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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 6 May 2007 09:22:03 +1000 (EST)
From:	Srihari Vijayaraghavan <sriharivijayaraghavan@...oo.com.au>
To:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PROBLEM] 2.6.21-git oops

[Sorry to reply to my own email, but I had some good development on this
problem]

--- Srihari Vijayaraghavan <sriharivijayaraghavan@...oo.com.au> wrote:
> Here's the first one (there a couple following this;
> the complete dmesg is at the bottom of this email):

It turns out the system is no go with 4 GB of RAM (4 * 1 GB modules): system
instability & SATA controller doesn't detect the drives (as I reported to
linux-ide:
http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06174.html).

With only 2 GB of RAM (with either pairs), system is very stable (surviving
many parallel kernel compiles for over 3 times longer than that of 4 GB), and
it detects & works fine with the SATA drives also.

Any advice on getting all of 4 GB to work reliably with SATA also?

Thanks

PS: Here's a dmesg of the all stably working 2 GB system, & the oopsy one with
4 GB.

Send instant messages to your online friends http://au.messenger.yahoo.com 
Download attachment "dmesg-2.6.21.1-2gigs" of type "application/octet-stream" (14199 bytes)

Download attachment "oops2-mm-2.6.21.1-libata-4gigs" of type "application/octet-stream" (20256 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ