linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: CPU-Test similar to Memtest?
Date: 7 Nov 2003 15:03:21 GMT	[thread overview]
Message-ID: <bogc7p$l07$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 1067379433.6281.575.camel@tubarao

In article <1067379433.6281.575.camel@tubarao>,
Thayne Harbaugh  <tharbaugh@lnxi.com> wrote:

| On Tue, 2003-10-28 at 09:05, Robert L. Harris wrote:
| > I'm going to run MEMTEST today when I get home and get a chance to make
| > a bootable CD
| 
| Memtest86 is good, but it isn't as good as it could be.  Many times I
| have seen it run 24 hours without error even though the the system has
| bad memory.
| 
| >  but I'm wondering if there might be a "CPUTEST" or such
| > utility anyone knows of that'll poke and prod a dual athalon real well
| > and make sure I don't have a flaky cpu.
| 
| Run Linpack (or other computationally intensive program) while
| monitoring ECC errors with either
| http://www.anime.net/~goemon/linux-ecc/files/
| or
| ftp://ftp.lnxi.com/pub/bluesmoke

I agree with almost everything you said, but I have seen cases in which
no CPU use would generate an error, but using heavy DMA io in addition
triggered the problem. If all else fails add your favorite disk test.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  reply	other threads:[~2003-11-07 22:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 16:05 CPU-Test similar to Memtest? Robert L. Harris
2003-10-28 16:17 ` Ciaran McCreesh
2003-10-28 17:06 ` Maciej Zenczykowski
2003-10-28 22:17 ` Thayne Harbaugh
2003-11-07 15:03   ` bill davidsen [this message]
2003-11-08  3:47     ` Samuel Flory

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='bogc7p$l07$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.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;
as well as URLs for NNTP newsgroup(s).