From owner-freebsd-current  Mon Aug  7  8:58: 8 2000
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 5948337B5D2
	for <current@FreeBSD.ORG>; Mon,  7 Aug 2000 08:58:03 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA87343;
	Mon, 7 Aug 2000 09:58:01 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA32453; Mon, 7 Aug 2000 09:57:45 -0600 (MDT)
Message-Id: <200008071557.JAA32453@harmony.village.org>
To: David Scheidt <dscheidt@enteract.com>
Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 07 Aug 2000 10:53:27 CDT."
		<Pine.NEB.3.96.1000807105052.95334A-100000@shell-1.enteract.com> 
References: <Pine.NEB.3.96.1000807105052.95334A-100000@shell-1.enteract.com>  
Date: Mon, 07 Aug 2000 09:57:45 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.NEB.3.96.1000807105052.95334A-100000@shell-1.enteract.com> David Scheidt writes:
: convince people that their memory is bad.  The only reliable way to test
: memory is with a hardware testor, or swapping known good memory in.

Yes.  while (1) do ; make world; done is a close second to a hardware
tester.

I can't tell you the number of times I've had flakey systems that made
people sure FreeBSD was busted.  A new CPU, mobo or memory fixed these
right up.  Troubleshooting that can be interesting...

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message