From owner-freebsd-current Mon Aug 7 12:52:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4F60F37BED3 for ; Mon, 7 Aug 2000 12:52:29 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA23678; Mon, 7 Aug 2000 14:52:19 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 7 Aug 2000 14:52:19 -0500 (CDT) From: Chris Dillon To: David Scheidt Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) In-Reply-To: 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, David Scheidt wrote: > 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. Many motherboards are unstable when you populate all DIMM slots. You generally have limitations to what types of DIMMs you can use (i.e. single-sided only, registered only, etc.) when you do populate all of them. The manual _should_ specify these limitations. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message