From: ebiederm@xmission.com (Eric W. Biederman)
To: "Stephen Gutknecht (linux-kernel)" <linux-kernel@i405.com>
Cc: "'David Lang'" <david.lang@digitalinsight.com>,
David Riley <oscar@the-rileys.net>,
linux-kernel@vger.kernel.org
Subject: Re: Better testing of hardware (was: Defective Read Hat)
Date: 22 Nov 2000 00:13:09 -0700 [thread overview]
Message-ID: <m1bsv832ey.fsf@frodo.biederman.org> (raw)
In-Reply-To: <0066CB04D783714B88D83397CCBCA0CD49AF@spike2.i405.net>
In-Reply-To: "Stephen Gutknecht's message of "Tue, 21 Nov 2000 13:39:17 -0800"
"Stephen Gutknecht (linux-kernel)" <linux-kernel@i405.com> writes:
> A Linux Kernel compile test does a really good job of testing the hard disk,
> RAM, and CPU... as it executes all types of instructions and the final
> output depends on all prior steps completing correctly. On a really fast
> system (> 900Mhz) might make sense to run it twice, once to "warm up" the
> CPU and other components. Most "benchmarks" just test speed, not the actual
> stability or data integrity (they write results to a device but don't check
> for data corruption, or they test only one device at a time, not all at
> once).
Also note that a Linux Kernel compile stresses memory because
of the very pointer loaded data structures of gcc. This means that
memory corruption is most likely to flip a bit in a pointer, and cause
a bad pointer.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-22 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 21:39 Better testing of hardware (was: Defective Read Hat) Stephen Gutknecht (linux-kernel)
2000-11-21 21:46 ` Dan Hollis
2000-11-21 23:22 ` Pavel Machek
2000-11-22 1:27 ` Fort David
2000-11-22 7:13 ` Eric W. Biederman [this message]
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=m1bsv832ey.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@i405.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar@the-rileys.net \
/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