From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/rmap.c:483!
Date: Wed, 23 Feb 2005 22:05:18 +0000 [thread overview]
Message-ID: <200502232205.18610.nick@linicks.net> (raw)
> But not all cases could be accounted in that way. If you
> report back that memtest86 ran cleanly...
Hugh,
Nothing to do with the 'problem' in this thread, but an aside that is perhaps
relevant.
On my main gateway, I couldn't get any kernel greater than 2.6.4 to run
without an 'oops' after x amount of time. It was always swapd or memory oops
that caused it.
I ran memtest86 a few times with no errors - reaseated everything, new fans
etc. etc. No go.
I upgraded memory - all 4 sticks - over Christmas, and after a few weeks
uptime, tried 2.4.10 again.
I have had no problems since - so perhaps I did have bad memory (it was old).
But all tests never showed anything untoward.
I was always suspicious why my 2.6.4 build ran OK, but newer builds always
failed. Could it be a subtle fault in memory whilst building kernels that
does it?
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2005-02-23 22:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 22:05 Nick Warne [this message]
2005-02-24 12:15 ` kernel BUG at mm/rmap.c:483! Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2005-02-23 20:41 Ammar T. Al-Sayegh
2005-02-23 20:54 ` Arjan van de Ven
2005-02-23 21:45 ` Ammar T. Al-Sayegh
2005-02-23 22:01 ` Arjan van de Ven
2005-02-23 22:46 ` Ammar T. Al-Sayegh
2005-02-24 8:38 ` Arjan van de Ven
2005-02-24 9:25 ` Ammar T. Al-Sayegh
2005-02-24 9:30 ` Arjan van de Ven
2005-02-28 10:43 ` Giacomo A. Catenazzi
2005-02-28 11:09 ` Arjan van de Ven
2005-02-23 21:31 ` Hugh Dickins
2005-02-23 22:38 ` Ammar T. Al-Sayegh
2005-02-24 5:31 ` Hugh Dickins
2005-02-24 13:25 ` Horst von Brand
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=200502232205.18610.nick@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
/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