From owner-freebsd-hackers  Thu Apr 13 21:09:55 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id VAA07778
          for hackers-outgoing; Thu, 13 Apr 1995 21:09:55 -0700
Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA07768
          for <freebsd-hackers@FreeBSD.org>; Thu, 13 Apr 1995 21:09:51 -0700
Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id WAA27524; Thu, 13 Apr 1995 22:13:47 -0600
Date: Thu, 13 Apr 1995 22:13:47 -0600
Message-Id: <199504140413.WAA27524@trout.sri.MT.net>
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Cc: pw@snoopy.MV.COM (Paul F. Werkowski), freebsd-hackers@FreeBSD.org
Subject: Re: 940804 (vaporware ;-) reboots the system either:
In-Reply-To: <199504131952.MAA10852@gndrsh.aac.dev.com>
References: <199504131904.PAA02469@snoopy.mv.com>
	<199504131952.MAA10852@gndrsh.aac.dev.com>
Reply-To: nate@sneezy.sri.com (Nate Williams)
From: nate@sneezy.sri.com (Nate Williams)
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

{ Software Memory test programs }
> 
> Though CHECKIT does a somewhat reasonable job I have seen memory that
> will run CHECKIT for 24 hours and still fail to run Unix or Novell
> server.  IMHO, the only real test (I guess this comes from 3 years
> of being a VLSI test engineer) is to run the stuff on a memory tester.

And, I have yet to see a memory test program that was able to diagnose
my memory problems.  I ran every memory program I could find, and even
talked to the developer of a popular commericial program to see if he
could help out.  It turned out my memory was fine, but my cache memory
was not.  However, the results were the same, corrupted memory.


Nate