From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Steve Youngs <steve@youngs.au.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
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: Fri, 21 Oct 2005 22:44:22 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.63.0510212233140.26585@deepthought.mydomain> (raw)
In-Reply-To: <microsoft-free.87pspybm4d.fsf@youngs.au.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed, Size: 1159 bytes --]
On Sat, 22 Oct 2005, Steve Youngs wrote:
>
> 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
>
At least the problem showed up, so the load on the power supply is not
a prime concern.
If you have the patience, first take out one of the 'good' sticks and
repeat with 2x1GB. If that works, it's probable the mobo can't drive
3x1GB, at least with the chip arrangement on those particular sticks.
OTOH, if it still fails at that address, perhaps that one stick is
suspect - in that case try swapping it and retesting.
Of course, if your manual is unclear about which slot maps where, you
might have to try permutations of 2 sticks on this approach. And that's
before messing with obscure and poorly-explained bios options to control
the memory timing and drive. Good Luck!
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2005-10-21 21:44 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 [this message]
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=Pine.LNX.4.63.0510212233140.26585@deepthought.mydomain \
--to=zarniwhoop@ntlworld.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®