From: Hugh Dickins <hugh@veritas.com>
To: Steve Youngs <steve@youngs.au.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.13.4 After increasing RAM, I'm getting Bad page state at prep_new_page
Date: Wed, 19 Oct 2005 17:59:33 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0510191741350.8481@goblin.wat.veritas.com> (raw)
In-Reply-To: <microsoft-free.877jc9jzwy.fsf@youngs.au.com>
On Thu, 20 Oct 2005, Steve Youngs wrote:
>
> A few days ago I increased my RAM from 0.5Gb to 3Gb and since then
> I've been getting `Bad page state at prep_new_page' errors at odd
> times. Here is a typical backtrace from my logs:
>
> Bad page state at prep_new_page (in process 'X', page c1f7bde0)
> flags:0x80000004 mapping:00000000 mapcount:-262144 count:0
It does look like bad memory, the single bit 0x40000 has got cleared
from the 0xffffffff which represents the expected mapcount 0 (for
reasons I won't go into, physical -1 represents logical 0 there).
If it were 0x800 which was cleared, I'd get excited, because that
would fit with a report from a few months back, which really did
not seem to be bad memory. But 0x40000 isn't so interesting, sorry!
The bad memory in question (the struct page at 0xc1f7bde0) is quite
low down, just below 32MB. Would I be right to guess that that you
inserted the new cards in such a way that the low memory is new RAM?
I suggest you try taking out that lowest card, and see what happens
then. Sometimes the kernel these days seems to find memory problems
that memtest86 does not (how long did you run it? overnight?).
You could try sending me all your "Bad page state" messages,
to check for correlations.
Hugh
next prev parent reply other threads:[~2005-10-19 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 15:21 Steve Youngs
2005-10-19 16:54 ` Ken Moffat
2005-10-21 21:23 ` Steve Youngs
2005-10-21 21:44 ` Ken Moffat
2005-10-19 16:59 ` Hugh Dickins [this message]
2005-10-21 21:29 ` Steve Youngs
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=Pine.LNX.4.61.0510191741350.8481@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@youngs.au.com \
/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®