public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ishikawa <ishikawa@yk.rim.or.jp>, linux-kernel@vger.kernel.org
Subject: Re: Q: boot time memory region recognition and clearing.
Date: Sat, 13 Jul 2002 17:09:40 +0200 (MEST)	[thread overview]
Message-ID: <200207131509.RAA24969@cave.bitwizard.nl> (raw)
In-Reply-To: <1026569717.9958.77.camel@irongate.swansea.linux.org.uk> from Alan Cox at "Jul 13, 2002 03:15:17 pm"

Alan Cox wrote:
> On Sat, 2002-07-13 at 11:08, Ishikawa wrote:
> > I have found that the particular motherboard (and memory sticks)
> > that I use at home tends to generate bogus memory problem 
> > warning messages when I use ecc module.
> > Motherboard is Gigabyte 7XIE4 that uses AMD751.
> > (Yes, AMD has now provides AMD76x series chipset for
> > newer CPUs.)
> > 
> > I say "bogus" because I have tested the hardware
> > many times using memtest86 and found that it doesn't
> > detect any memory errors even 
> 
> memtest86 isnt (except on the very very latest versions) aware of ECC.
> It sees the memory after the ECC rescues minor errors so if the RAM has
> errors but ECC just about saves you it will show up clean

A friend of mine had "subtle memory problems". He tested the memory
using memtest86. No errors running for hours. 

Then he did:
	bank1 = malloc (bignum); 
	bank2 = malloc (bignum); 
	srand (seed);
	bash (bank1);
	srand (seed); 
	bash (bank2); 

	if (memcmp (bank1, bank2) != 0)
		Memory error!

and quickly found a memory error on the first pass. 

It turns out you can memtest all you want, but different access
patterns may cause different errors. In some cases memtest86 doesn't
detect problems, while other stuff does.....

				Roger. 


-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

  reply	other threads:[~2002-07-13 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13 10:08 Q: boot time memory region recognition and clearing Ishikawa
2002-07-13 14:15 ` Alan Cox
2002-07-13 15:09   ` Rogier Wolff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-13 14:19 Chiaki
2002-07-14  8:20 ` Eric W. Biederman
2002-07-14 15:38   ` Ishikawa
2002-07-14 20:26     ` Eric W. Biederman
2002-07-13 23:27 Chiaki
2002-07-18  2:08 Chiaki

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=200207131509.RAA24969@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ishikawa@yk.rim.or.jp \
    --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