All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Youngs <steve@youngs.au.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: Ken Moffat <zarniwhoop@ntlworld.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:23:14 +1000	[thread overview]
Message-ID: <microsoft-free.87pspybm4d.fsf@youngs.au.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0510191730570.23833@deepthought.mydomain> (Ken Moffat's message of "Wed, 19 Oct 2005 17:54:20 +0100 (BST)")

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

* Ken Moffat <zarniwhoop@ntlworld.com> writes:

  > On Thu, 20 Oct 2005, Steve Youngs wrote:
  >> 
  >> RAM.  But I've run memtest86 (version 3.2) over the RAM and no errors
  >> were found.

  >  Steve,

  > this is almost certainly a hardware problem.  I'm not saying that the
  > RAM is actually defective, it could be that the motherboard doesn't
  > reliably support that much memory, or even a weak powersupply.

  > I prefer to use memtest86+ for recent hardware, but I'm sure
  > memtest86 can find errors if you give it long enough (on a 1.8GHz
  > athlon64 with a mere 2GB of memory, several hours were needed -
  > the memory was good, but the mobo couldn't drive that much at
  > full speed).

I gave memtest86+ a shot, and after about 18 hours it came up with...

  Test:            8
  Pass:            7
  Failing Address: 00008072bf0 - 128.1MB
  Good:            00000000
  Bad:             00000100
  Err-Bits:        00000100
  Count:           1

  >  3GB sounds an awful lot for an athlon - 2x1GB and 2x512MB, I suppose. 

3x1GB

  >  Of course, if it's a PSU problem related to excessive power to memory + 
  > disk(s) + graphics card, memtest86 is unlikely to trigger it.

And to track _that_ down I'll have to play "mix'n'match" with the
hardware.  Something that I can't do right now (financially, and,
time). :-(

Sounds like I'm just going to have to put up with it for the time
being.

Thanks anyway, Ken.

-- 
|---<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:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 15:21 2.6.13.4 After increasing RAM, I'm getting Bad page state at prep_new_page Steve Youngs
2005-10-19 16:54 ` Ken Moffat
2005-10-21 21:23   ` Steve Youngs [this message]
2005-10-21 21:44     ` Ken Moffat
2005-10-19 16:59 ` Hugh Dickins
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=microsoft-free.87pspybm4d.fsf@youngs.au.com \
    --to=steve@youngs.au.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zarniwhoop@ntlworld.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 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.