https://bugzilla.novell.com/show_bug.cgi?id=231220 ------- Comment #1 from seife@novell.com 2007-01-01 10:23 MST ------- Created an attachment (id=111234) --> (https://bugzilla.novell.com/attachment.cgi?id=111234&action=view) oops -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 kkeil@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |seife@novell.com ------- Comment #3 from kkeil@novell.com 2007-01-02 09:03 MST ------- Hmm 768 MB -> 2GB maybe only make a difference with not full 32 bit DMA and wrong DMA settings for the network card. Or bad memory. Some more info about the HW are needed for further investigation. Please also run memtest for a night to rule out bad memory (or wrong memory timing). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|seife@novell.com | ------- Comment #5 from seife@novell.com 2007-01-02 10:01 MST ------- Created an attachment (id=111297) --> (https://bugzilla.novell.com/attachment.cgi?id=111297&action=view) hwinfo --all --log hwinfo.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|seife@novell.com | ------- Comment #7 from seife@novell.com 2007-01-02 11:09 MST ------- wired. It is not possible to create considerable network traffic via a wireless interface ;-)) I only have a 100mbit network, though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 ------- Comment #9 from seife@novell.com 2007-01-03 06:11 MST ------- I only got the oops once. I can not prove it is NFS-related, i just guessed that since i am seeing hard hangs quite frequently when copying via NFS and writing to the local ext3 drive. I speculated that this might have to do with highmem, buffering and actually running out of lowmem. I will try to wget some large DVD images via http or ftp and see if the machine hangs up there, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|seife@novell.com | ------- Comment #10 from seife@novell.com 2007-01-14 05:19 MST ------- I have rebuilt my filesystems, they were all with 1k blocksize due to the yast2 bug until close-to-goldmaster-10.2. I can no longer get the machine to hang now (but it was not too clearly reproducible before...). My _uneducated_ guess what happened is: - write performance was abysmal due to ext3 with 1k blocksize - nfs reads with 10mb/second into (highmem?) fs cache - ext3 tries to write out, performance is bad - something in ext3 needs lowmem (inode cache maybe? something that needs much more space due to the 1k blocksize?) - now somewhere in a driver (with interrupts turned off, because it does not even react to sysrq) memory needs to be allocated, but it does not succeed. Maybe the lowmem accounting is wrong somewhere, so that there _should_ be memory free to use, but isn't? - With the 4k blocksize it does not happen, because the disk simply is much faster writing out than the network is filling the buffers? With the 1k blocksize, the machine was also very "jumpy" before locking up, means that i had latencies of 10's of seconds in the console when doing anything (ls for example), which would IMO support the "memory pressure" theory. This could of course be totally off topic :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |npiggin@novell.com |maintainers@forge.provo.nove| |ll.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=231220 ------- Comment #13 from seife@novell.com 2007-01-22 01:09 MST ------- I have no 1k filesystems anymore (which really improved the performance of this machien), and it has not hung anymore. The hangs could theoretically also be caused by a rogue driver (i am using the nozomi driver for my 3g datacard, but i only experienced hangs with it when i actually used the card), but actually the only thing that has changed since two weeks was that i changed the blocksize of all my filesystems. Oh - in case this might matter - i am using cryptoloop for my home, which also had 1k blocksize before... Well, maybe this bug report is an intertwingled mess up of unrelated issues, i am even not sure at all that the oops has anything to do with the former hard lockups, and since i changed the block size, i have not had any problems. As i understand it, the only way a memory problem could lock the machine hard would be a failing memory allocation with interrupts turned off... Maybe this is my call to fame to audit all the paths where this could happen in the kernel... once i have learned enough to actually read more than the most trivial kernel code. Executive summary: feel free to close this one as "worksforme". I will try to reproduce it, but other stuff has surely higher priority for now. Maybe somewhen we will stumble about something that will explain why this happened :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.