From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Srihari Vijayaraghavan" <sriharivijayaraghavan@yahoo.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] 2.6.21-git oops
Date: Sun, 6 May 2007 01:37:02 +0200 [thread overview]
Message-ID: <6bffcb0e0705051637k6e39bcds76456ea5ff5f11c5@mail.gmail.com> (raw)
In-Reply-To: <4968.12298.qm@web52606.mail.re2.yahoo.com>
Hi Srihari,
On 06/05/07, Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au> wrote:
> [Sorry to reply to my own email, but I had some good development on this
> problem]
>
> --- Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.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.
>
This looks like a bad RAM problem too me. Check the RAM memory
http://www.memtest.org/
(Removed from the list of known regressions
http://kernelnewbies.org/known_regressions)
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
next prev parent reply other threads:[~2007-05-05 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 23:22 Srihari Vijayaraghavan
2007-05-05 23:37 ` Michal Piotrowski [this message]
2007-05-06 1:27 ` Srihari Vijayaraghavan
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 20:42 Srihari Vijayaraghavan
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=6bffcb0e0705051637k6e39bcds76456ea5ff5f11c5@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®