From owner-freebsd-questions Tue Apr 17 19: 3:42 2001 Delivered-To: freebsd-questions@freebsd.org Received: from omta04.mta.everyone.net (sitemail.everyone.net [216.200.145.35]) by hub.freebsd.org (Postfix) with ESMTP id BA17037B621 for ; Tue, 17 Apr 2001 19:03:34 -0700 (PDT) (envelope-from k_greenwood1@sluggy.net) Received: from sitemail.everyone.net (reports [216.200.145.62]) by omta04.mta.everyone.net (Postfix) with ESMTP id A449A4F949; Tue, 17 Apr 2001 19:03:34 -0700 (PDT) Received: by sitemail.everyone.net (Postfix, from userid 99) id 9676E36EE; Tue, 17 Apr 2001 19:03:34 -0700 (PDT) Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 X-Mailer: MIME-tools 4.104 (Entity 4.117) Date: Tue, 17 Apr 2001 19:03:34 -0700 (PDT) From: K.Greenwood To: "Mike Dorin" Cc: questions@freebsd.org Subject: Re: Lockup problem continues...was memory tools Reply-To: k_greenwood1@sluggy.net X-Originating-Ip: [216.95.179.96] Message-Id: <20010418020334.9676E36EE@sitemail.everyone.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off, my knowledge is limited (read "relative newbie") but I have twice experienced similar situations that you are in. The first time it was mem, but you already checked that. Maybe you could test the HD? When I was having problems it would just get to a certain point and lock up. When I tried formatting it (via DOS) it would also lock up. Popped in a new HD and my problems disappeared. Hope it helps. --- "Mike Dorin" > wrote: > >Ted, >Thanks for your suggestion. I did just that. I removed half the >chips, got two huge builds going..watched it lock up. Swapped >the memory and did it again. > >Since the machine just locks up...it does not panic..there >are no strings or error messages, is there any >way to point a fingure at the problem? > >Thanks, >-Mike > >>From: "Ted Mittelstaedt" >>To: "Mike Dorin" , >>Subject: RE: Memory Tools for FreeBSD? >>Date: Sun, 15 Apr 2001 21:59:00 -0700 >> >>I've found that there's only one way to really know if your >>memory is up to snuff - put it into a SIMM/DIMM tester. >>Even then, all that will do is tell you that the memory >>meets it's own specs - it won't tell you if the memory is >>actually compatible with the system that you put it in. >> >>Failing that, what your doing (attempting to compile >>programs) is a much better test than most of those >>so-called "pc testing" programs like Checkit and so on. >>I've seen plenty of systems that passed memory tests >>but broke on FreeBSD. OS/2 is also a very good memory >>tester - if you can't boot an OS/2 bootable floppy without >>it trapping, then bad ram is definitely indicated. >> >>What most people do when suspecting bad ram is to take half >>the chips out, retry the thing that caused it to crash, then >>see if the problem is still there. If it is, then swap out those >>chips with the half that you first took out and retry again >>and see if the problem goes away. >> >>Ted Mittelstaedt tedm@toybox.placo.com >>Author of: The FreeBSD Corporate Networker's Guide >>Book website: http://www.freebsd-corp-net-guide.com >> >> >> >-----Original Message----- >> >From: owner-freebsd-questions@FreeBSD.ORG >> >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Mike Dorin >> >Sent: Sunday, April 15, 2001 2:30 PM >> >To: questions@FreeBSD.ORG >> >Subject: Memory Tools for FreeBSD? >> > >> > >> >My new freebsd server crashes when I try to build things like ssh. >> >I suspect it is a memory problem. Are there any tools that could >> >help me exercise things like memory to be sure? >> >-Mike >> >_________________________________________________________________ >> >Get your FREE download of MSN Explorer at http://explorer.msn.com >> > >> > >> >To Unsubscribe: send mail to majordomo@FreeBSD.org >> >with "unsubscribe freebsd-questions" in the body of the message >> > > >_________________________________________________________________ >Get your FREE download of MSN Explorer at http://explorer.msn.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message _____________________________________________________________ Sluggy.Net: The Sluggy Freelance Community! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message