Date: Mon, 7 Aug 2000 14:52:19 -0500 (CDT) From: Chris Dillon <cdillon@wolves.k12.mo.us> To: David Scheidt <dscheidt@enteract.com> Cc: Warner Losh <imp@village.org>, current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) Message-ID: <Pine.BSF.4.21.0008071449190.22965-100000@mail.wolves.k12.mo.us> In-Reply-To: <Pine.NEB.3.96.1000807110143.95334B-100000@shell-1.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Aug 2000, David Scheidt wrote: > On Mon, 7 Aug 2000, Warner Losh wrote: > > :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. > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0008071449190.22965-100000>