mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Youngs <steve@youngs.au.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: Hugh Dickins <hugh@veritas.com>
Subject: Re: 2.6.13.4 After increasing RAM, I'm getting Bad page state at prep_new_page
Date: Sat, 22 Oct 2005 07:29:11 +1000	[thread overview]
Message-ID: <microsoft-free.87ll0mblug.fsf@youngs.au.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0510191741350.8481@goblin.wat.veritas.com> (Hugh Dickins's message of "Wed, 19 Oct 2005 17:59:33 +0100 (BST)")

[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]

* Hugh Dickins <hugh@veritas.com> writes:

  > 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

  > 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?

No.  All the memory is new RAM.  I originally had 2x256MB, and I
replaced those with 3x1GB.  Sorry if the Subject header was a bit
misleading. 

  > 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?).

When I had posted the message I had only let it run through all tests
once.  I have since let it run for about 18 hours, where it came up
with a single error (as reported in my reply to Ken).

  > You could try sending me all your "Bad page state" messages,
  > to check for correlations.

OK, I'll send those to you off-list.

Thanks very much, Hugh.

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|                   Te audire no possum.                   |
|             Musa sapientum fixa est in aure.             |
|----------------------------------<steve@youngs.au.com>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]

      reply	other threads:[~2005-10-21 21:29 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
2005-10-21 21:29   ` Steve Youngs [this message]

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=microsoft-free.87ll0mblug.fsf@youngs.au.com \
    --to=steve@youngs.au.com \
    --cc=hugh@veritas.com \
    --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

Powered by JetHome