From owner-freebsd-current Mon Aug 7 9: 6: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id DF5EC37B7BF for ; Mon, 7 Aug 2000 09:05:57 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id LAA11093; Mon, 7 Aug 2000 11:05:55 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Mon, 7 Aug 2000 11:05:55 -0500 (CDT) From: David Scheidt To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) In-Reply-To: <200008071557.JAA32453@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, Warner Losh wrote: :In message 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. Ah, that tells you have a problem. It unfortunatly, doesn't distinguish a bad memory module from a bad memory bus. One of my abits blew up a bit ago with SIGSEGVs, I swapped memory in and around till I got to the point that I realized that as long as I didn't populate the last DIMM slot, it worked fine. It's not long for this earth, that machine. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message