public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fort David <epopo@onetelnet.fr>
To: "Stephen Gutknecht (linux-kernel)" <linux-kernel@i405.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Better testing of hardware (was: Defective Read Hat)
Date: Wed, 22 Nov 2000 02:27:00 +0100	[thread overview]
Message-ID: <3A1B20E4.25871E33@onetelnet.fr> (raw)
In-Reply-To: <0066CB04D783714B88D83397CCBCA0CD49AF@spike2.i405.net>

"Stephen Gutknecht (linux-kernel)" wrote:

> Part of the issue is that there exists no "easy to use" standardized test
> software.  Full 32-bit concurrent use of many devices can reveal problems
> that users do not often see in normal applications.
>
> One major hardware review site found stability problems with the Intel
> Pentium 3 1130Mhz processor that ultimately lead to Intel delaying the
> release -- it passed all tests but not a compile of the Linux Kernel!  This
> was on more than 3 different processors.
> http://www.tomshardware.com/cpu/00q3/0008281/pentiumiii-04.html
>
> 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).
>
> What a Linux kernel compile DOESN'T test is the network interfaces and video
> cards.
>
>

Compiling over NFS with compilation lines producing some kind of openGL
animation ?

--
%-------------------------------------------------------------------------%
% FORT David,                                                             %
% 7 avenue de la morvandière                                   0240726275 %
% 44470 Thouare, France                                epopo@onetelnet.fr %
% ICU:78064991   AIM: enlighted popo             fort@irin.univ-nantes.fr %
%--LINUX-HTTPD-PIOGENE----------------------------------------------------%
%  -datamining <-/                        |   .~.                         %
%  -networking/flashed PHP3 coming soon   |   /V\        L  I  N  U  X    %
%  -opensource                            |  // \\     >Fear the Penguin< %
%  -GNOME/enlightenment/GIMP              | /(   )\                       %
%           feel enlighted....            |  ^^-^^                        %
%                           http://ibonneace.dnsalias.org/ when connected %
%-------------------------------------------------------------------------%



-
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/

  parent reply	other threads:[~2000-11-22  0:59 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 [this message]
2000-11-22  7:13 ` Eric W. Biederman

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=3A1B20E4.25871E33@onetelnet.fr \
    --to=epopo@onetelnet.fr \
    --cc=linux-kernel@i405.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