[Sorry to reply to my own email, but I had some good development on this problem] --- Srihari Vijayaraghavan <[email protected]> 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/[email protected]/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
Attachment:
dmesg-2.6.21.1-2gigs
Description: 569209996-dmesg-2.6.21.1-2gigs
Attachment:
oops2-mm-2.6.21.1-libata-4gigs
Description: 2887524220-oops2-mm-2.6.21.1-libata-4gigs
- Follow-Ups:
- Re: [PROBLEM] 2.6.21-git oops
- From: "Michal Piotrowski" <[email protected]>
- Re: [PROBLEM] 2.6.21-git oops
- Prev by Date: [PATCH 3/4] nfsctl: Use path_component_lookup
- Next by Date: Re: 2.6.21-mm1
- Previous by thread: [PROBLEM] 2.6.21-git oops
- Next by thread: Re: [PROBLEM] 2.6.21-git oops
- Index(es):