From: Stephen Satchell <list@fluent2.pyramid.net>
To: Edgar Toernig <froese@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (OT) md5sum proving to be an EXCELLENT memory test
Date: Mon, 21 Apr 2003 06:46:30 -0700 [thread overview]
Message-ID: <5.2.0.9.0.20030421063052.00a706c0@fluent2.pyramid.net> (raw)
In-Reply-To: <3EA3EC75.35988618@gmx.de>
At 03:04 PM 4/21/03 +0200, you wrote:
>Stephen Satchell wrote:
> >
> > The "good memory test suite" I have didn't catch it. The copy method you
> > suggest didn't catch it. The BIOS memory check didn't catch it. Only the
> > linux compile method -- mentioned on this list -- did catch it. And so did
> > using md5sum on very long files.
>
> >From my experience it's not bad RAM that shows these failures but
>an overheating CPU.
>
>Ciao, ET.
Well, I just finished an overnight test on the server in question. If it's
an overheating CPU, then I don't understand how replacing the RAM stick
fixes the problem so that it runs without failure for 12 hours. An
overheating RAM stick could do it, too.
In tracing through my collection of computers, I have found others with
this flaky RAM that show intermittent failures using md5sum that other
tests don't find (including kernel compiles). All the failing RAM comes
from the same manufacturer and batch. I think it's just barely marginal
memory, myself. Once I replace it all, I should stop seeing the
every-other-fortnight problems that have plagued me for the past year.
It also means I need to check the junk pile to see if the failed systems
have RAM trouble at their heart.
(N.B.: This little exercise has opened my eyes some little bit. Easter
was a great time to bring down the servers one by one, blow the crap out of
them with compressed air, and check the RAM. And replace questionable
RAM. I'm also going to have a little talk with the computer store that
sold me a "white box" computer with PC66 SDRAM when PC100 SDRAM was called
for.)
Here's how bad some of this stuff was: I took an ASUS P5A-B board with an
AMD K6-II, slowed the bus down to 87 MHz from 100 MHz, and the damn memory
fails at the slower bus speed. Every loose stick from that batch of RAM
shows the failure. (memtest86 caught the errors, by the way, so
diagnostics aren't completely worthless.)
Kingston, Viking, and Micron are getting more of my business.
--
X -> unknown; Spurt -> drip of water under pressure
Expert -> X-Spurt -> Unknown drip under pressure.
next prev parent reply other threads:[~2003-04-21 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 3:11 Linux 2.5.68 Linus Torvalds
2003-04-20 4:57 ` Ben Collins
2003-04-20 13:23 ` irq balancing; kernel vs. userspace Sean Neakums
2003-04-20 18:31 ` Arjan van de Ven
2003-04-20 18:37 ` Kevin P. Fleming
2003-04-20 19:10 ` Arjan van de Ven
2003-04-20 18:55 ` Sean Neakums
2003-04-20 20:11 ` Zwane Mwaikambo
[not found] ` <Pine.LNX.4.50.0304201605360.17265-100000@montezuma.mastece nde.com>
2003-04-20 20:43 ` (OT) md5sum proving to be an EXCELLENT memory test Stephen Satchell
2003-04-20 21:58 ` Leonard Milcin, Jr
2003-04-20 23:45 ` Stephen Satchell
[not found] ` <3EA3EC75.35988618@gmx.de>
2003-04-21 13:46 ` Stephen Satchell [this message]
2003-04-23 19:33 ` 2.5.68: net/decnet/dn_route.c doesn't compile Adrian Bunk
2003-04-23 19:46 ` Steven Whitehouse
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=5.2.0.9.0.20030421063052.00a706c0@fluent2.pyramid.net \
--to=list@fluent2.pyramid.net \
--cc=froese@gmx.de \
--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
all inboxes | Powered by JetHome®