| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <453f585d.299e45f8.4666.371b@mx.google.com> Date: Wed, 25 Oct 2006 22:28:02 +1000 From: "Michael" <michael.sallaway@...il.com> To: <ray-gmail@...rabbit.org> Cc: <linux-kernel@...r.kernel.org> Subject: RE: PROBLEM: Oops when doing disk heavy disk I/O > -----Original Message----- > From: Ray Lee [mailto:madrabbit@...il.com] > Sent: Wednesday, 25 October 2006 2:13 PM > > Try swapping out the RAM (or getting it down to 1Gig). Try a really > old kernel, such as debian's 2.6.8 package. > > Ray Well, what do you know -- that seems to have fixed it! I took out one stick of RAM (so it's down to 1 gig) and it seems to work fine, now, without any boot parameters or anything. (mind you, murphy's law will dictate that it'll crash about 30 seconds after I send this...) I'm amazed at that -- but I'm not going to look a gift horse in the mouth, this has been frustrating me for far too long. :-) Although, having said that, I'm curious... It is working because there's only 1 gig of RAM in there, or because it's only a single stick (ie. not dual-channel)? It works fine with both sticks, individually, just not both together... I wonder what the cause of it actually is... Thanks heaps for the suggestion! Cheers, Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists