From owner-freebsd-questions@FreeBSD.ORG Fri Nov 26 05:24:45 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 643D516A4CE for ; Fri, 26 Nov 2004 05:24:45 +0000 (GMT) Received: from skippyii.compar.com (old.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C436843D49 for ; Fri, 26 Nov 2004 05:24:44 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [69.193.82.185])iAQ5VrU2064374; Fri, 26 Nov 2004 00:31:53 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001a01c4d377$e144fbe0$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Rob" , "FreeBSD" References: <6FC9F9894A9F8C49A722CF9F2132FC220276581D@ms05.mailstreet2003.net><20041125234948.R27818@april.chuckr.org> <41A6B7CC.90605@yahoo.com> Date: Fri, 26 Nov 2004 00:22:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: Re: Is this a sign of memory going bad? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 05:24:45 -0000 > Chuck Robey wrote: > > On Thu, 25 Nov 2004, Haulmark, Chris wrote: > > > > > >>Someone broke the silence: > >> > >> > >>>On Thu, Nov 25, 2004 at 04:05:53PM -0500, Lowell Gilbert wrote: > >>> > >>>>Jonathon McKitrick writes: > >>>> > >>>> > >>>>>This is what I get from make buildworld. I've gotten signal 10, > >>>>>11, and now 5. > >>>>> > >>>>>Is this bad memory? > >>>> > >>>>That's a reasonable guess, but the only way to tell for sure is to > >>>>test it. > >>> > >>>Is there a port to do this, or do I have to take it out and take it > >>>somewhere else to get it tested? > >>> > >>>jm > >> > >>sysutils/memtest in the ports. > > > > > > I don't want to embarrass anyone here, but something needs to be said. > > Note this next sentence carefully: THERE IS NO SUCH THING AS A WORKING > > MEMORY TEST PROGRAM!!! > > What about the BIOS RAM test? I mean the counter that you can interrupt with > the ESC key, at the beginning of the boot process? Will that reliably indicate > problems with the RAM, or is that test also rubbish? That just tests that the RAM is accessible (ie, electrical interface is sound). -- Matt Emmerton