From owner-freebsd-current Fri Aug 4 13:47:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mike.dhis.org (hiper1-d54.stk.cwnet.com [209.142.56.54]) by hub.freebsd.org (Postfix) with ESMTP id 6835B37B65F for ; Fri, 4 Aug 2000 13:47:44 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (ogre.lan [192.168.100.1]) by mike.dhis.org (Postfix) with ESMTP id AC15BD7; Fri, 4 Aug 2000 13:47:42 -0700 (PDT) Message-ID: <398B2BEE.CA9BD5CD@es.co.nz> Date: Fri, 04 Aug 2000 13:47:42 -0700 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Hocking Cc: current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) References: <200008041318.IAA60387@bloop.craftncomp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking wrote: > > About a week ago, I complained of mysterious Sig 11s during a make world. > After some experimentation, a PC100 DIMM was found to be better suited for a > 66MHz memory bus in another machine, who obligingly donated a DIMM in return > that actually works with a 100MHz bus. I think the trip from Australia and > this Texas heat finally pushed the dodgy one over the edge. Have you tried any memory testing routines such as memtest86 ? Its the only you write to a floppy and it runs before any bootstrap kicks in -- independant of the OS -- and takes around 18 hours for a single pass. It appears to be quite a comprehensive torture test. If so, how did that dodgy DIMM perform? (The reason I ask is that I'm interested in knowing if these tests can reveal the problems that building world did in your situation.) -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message