From owner-freebsd-questions Mon Jan 14 12:46:32 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id D3B4137B41F for ; Mon, 14 Jan 2002 12:46:12 -0800 (PST) Received: from colt.ncptiddische.net (ppp-338.wobline.de [212.68.71.59]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g0EKk2g16501; Mon, 14 Jan 2002 21:46:02 +0100 Received: from tisys.org (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g0EKlMX80821; Mon, 14 Jan 2002 21:47:23 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g0EKkSU06244; Mon, 14 Jan 2002 21:46:28 +0100 (CET) (envelope-from nils) Date: Mon, 14 Jan 2002 21:45:52 +0100 From: Nils Holland To: "Richard E. Hawkins" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: init 1 triggers hardware fault Message-ID: <20020114214552.A6088@tisys.org> Mail-Followup-To: "Richard E. Hawkins" , freebsd-questions@FreeBSD.ORG References: <200201142014.g0EKE3A00327@fac13.ds.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200201142014.g0EKE3A00327@fac13.ds.psu.edu>; from dochawk@psu.edu on Mon, Jan 14, 2002 at 03:14:03PM -0500 X-Operating-System: FreeBSD jodie.ncptiddische.net 4.5-RC FreeBSD 4.5-RC X-Machine-Uptime: 9:35PM up 9:35, 1 user, load averages: 0.20, 0.05, 0.02 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jan 14, 2002 at 03:14:03PM -0500, Richard E. Hawkins stood up and spoke: > > I have been having hardware freezes since ibm swapped the motherboard > on my A21p. These freezes happen both under freebsd and win98. The folloeing may or may not help, but you should probably consider running memtest86, which is available for free at http://www.memtest86.com First and foremost, this software tests your memory. It is indeed possible that the memory is your problem, but even if not, memtest86 might still be helpful. I have seen it crash some other unstable machines even though the RAM was fine. Also, I've seen that memtest86, especially when letting it run its advanced tests for a few hours, really makes the CPU temperature rise, so if you do indeed have a heat problem, this should trigger at (as a comparison, my 1 Ghz Athlon seems to report around 30-35 degrees celsius when idle, under compilation stress it seems to go up until 45 degress max, but memtest86 has gotten it to go to even 50 degrees! Hardware that is not properly cooled or has a heat problem should probably crash under memtest86's load). As far as finding out what's really wrong, I can tell you that memtest86 will tell you what parts of memory it had problems with during the test. It cannot tell you about other components in the system, however. Still, whenever a machine seems unstable, I first of all let memtest86 run on it and see what happens. Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message