From owner-freebsd-hackers  Mon Jun 24 10:01:02 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA05363
          for hackers-outgoing; Mon, 24 Jun 1996 10:01:02 -0700 (PDT)
Received: from xenon.chromatic.com (xenon.chromatic.com [199.5.224.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA05353
          for <hackers@freebsd.org>; Mon, 24 Jun 1996 10:01:00 -0700 (PDT)
Received: from server1.chromatic.com (server1.chromatic.com [199.5.224.120]) by xenon.chromatic.com (8.7.5/8.7.3) with ESMTP id KAA00652; Mon, 24 Jun 1996 10:00:27 -0700 (PDT)
Received: from localhost (hua@localhost) by server1.chromatic.com (8.7.5/8.7.3) with SMTP id KAA16970; Mon, 24 Jun 1996 10:00:26 -0700 (PDT)
Message-Id: <199606241700.KAA16970@server1.chromatic.com>
X-Authentication-Warning: server1.chromatic.com: hua owned process doing -bs
X-Authentication-Warning: server1.chromatic.com: Host hua@localhost didn't use HELO protocol
X-Mailer: exmh version 1.6.4 10/10/95
To: Don Yuniskis <dgy@rtd.com>
cc: jsigmon@www.hsc.wvu.edu (Jeremy Sigmon), hackers@freebsd.org,
        hua@xenon.chromatic.com
Subject: Re: Memory tests ... 
In-reply-to: Your message of "Mon, 24 Jun 1996 06:23:01 PDT."
             <199606241323.GAA29600@seagull.rtd.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 24 Jun 1996 10:00:26 -0700
From: Ernest Hua <hua@chromatic.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> > According to the systems people around here, the best way to test memory is
> > to put it into a Novell server.  If the memory is flakey it will let
> > you know fast. (ABEND???)
> > I thinks someone around here has a 4.1 2 user box setup just for that
> > purpose.
> 
> Are people looking for *exhaustive* tests, "quick and dirty" tests,
> diagnostic tests, or what?  There are different solutions for each
> of these.  But I think just the "make world" style tests add very little
> value (tho' prehaps, they are probably easiest to invoke...)

I would prefer a thorough set of tests such as some reasonably optimized
1's and 0's test.  I'm not familiar with algorithms for testing "flaky"
versus "stuck".

Ern