From: Tejun Heo <htejun@gmail.com>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Cc: linux-ide@vger.kernel.org, conke.hu@gmail.com
Subject: Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem
Date: Sun, 06 May 2007 11:33:03 +0200 [thread overview]
Message-ID: <463DA0CF.8080508@gmail.com> (raw)
In-Reply-To: <754241.548.qm@web52606.mail.re2.yahoo.com>
Srihari Vijayaraghavan wrote:
> I had a significant breakthrough: when I removed two out of four 1 GB modules
> (just a stab in the dark to see if the system stability problem I reported to
> LKML ( http://marc.info/?l=linux-kernel&m=117813911431765&w=2 ; a few sample
> oops messages attached for reference) goes away, I stuck a gold mine: now the
> SATA controller detects both the drives :-)).
>
> So, it'd seem the SATA controller wouldn't work fine when one has a lot of RAM
> on this board. The manual/manufacture's website claim it supports 8 GB of DDR2
> 800, while I only have 4, yet there are a few severe problems already: like
> this SATA drive detection problem & the system instability.
>
> I now got things working very reliably (even without pci=nomsi) with 2 GB of
> RAM (3 times longer kernel compile torture time with 2 GB, without kernel
> issues, with both pairs of RAM individually, compared with all of 4 GB where
> the system is plagued with instability). I intent to check how far below 4095M
> I could use mem= parameter with, without destablising the system, assuming if
> at all mem= parameters going to help.
>
> For the record, here's the complete dmesg of the current working system as an
> attachment (dmesg-2.6.21.1-2gigs):
>
> Thank you for your insight into the problem. If there are any tricks involved
> in making use of all 4 GB of RAM with SATA drives & with system stability,
> I'll be very happy to learn them :-)).
It might be that you just have a bad ram module. Does the machine work
properly if you exchange the installed two modules with the other two?
memtet86 time, I guess.
--
tejun
next parent reply other threads:[~2007-05-06 9:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <754241.548.qm@web52606.mail.re2.yahoo.com>
2007-05-06 9:33 ` Tejun Heo [this message]
2007-05-07 20:37 ` ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem Srihari Vijayaraghavan
2007-05-08 8:39 ` Tejun Heo
2007-05-08 9:35 ` Srihari Vijayaraghavan
2007-05-08 11:12 ` Tejun Heo
2007-05-08 11:16 ` Tejun Heo
2007-05-08 12:42 ` Srihari Vijayaraghavan
2007-05-08 12:39 ` Srihari Vijayaraghavan
2007-05-08 13:35 ` Tejun Heo
2007-05-08 15:00 ` Conke Hu
2007-05-08 15:03 ` Tejun Heo
2007-05-13 5:05 ` Srihari Vijayaraghavan
2007-05-14 9:10 ` Tejun Heo
2007-05-18 12:39 ` Srihari Vijayaraghavan
2007-05-18 12:46 ` Tejun Heo
2007-05-18 13:18 ` [PATCH] ahci: disable 64bit dma on sb600 Tejun Heo
2007-05-18 14:19 ` Srihari Vijayaraghavan
2007-05-18 14:23 ` Tejun Heo
2007-05-21 23:58 ` Jeff Garzik
2007-05-08 9:40 ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem Srihari Vijayaraghavan
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 12:32 Srihari Vijayaraghavan
2007-05-03 14:44 ` Tejun Heo
2007-05-04 1:48 ` Srihari Vijayaraghavan
2007-05-04 6:41 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463DA0CF.8080508@gmail.com \
--to=htejun@gmail.com \
--cc=conke.hu@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sriharivijayaraghavan@yahoo.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.