From owner-freebsd-questions Tue Mar 4 18:55:24 2003 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 5A66937B401 for ; Tue, 4 Mar 2003 18:55:23 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-52.dsl.lsan03.pacbell.net [63.207.60.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E038443FE9 for ; Tue, 4 Mar 2003 18:55:21 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 8C87366B37; Tue, 4 Mar 2003 18:55:21 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 6F0AA110C; Tue, 4 Mar 2003 18:55:21 -0800 (PST) Date: Tue, 4 Mar 2003 18:55:21 -0800 From: Kris Kennaway To: Bsd Neophyte Cc: Tuc , freebsd-questions@FreeBSD.ORG Subject: Re: still can't resolve these system reboots... help please Message-ID: <20030305025521.GA94920@rot13.obsecurity.org> References: <200303041302.h24D2erk009815@himinbjorg.ttsg.com> <20030304233008.40599.qmail@web20109.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <20030304233008.40599.qmail@web20109.mail.yahoo.com> User-Agent: Mutt/1.4i 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 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 04, 2003 at 03:30:08PM -0800, Bsd Neophyte wrote: > can faulty hardware be ruled out then? No. You can't exhaustively test the hardware using software. You can only test some things: what you have shown is that none of the things that burn* does cause your system to reboot. The only way you can rule out hardware failure completely is to replace it component by component and see if the problem persists. Your problems certainly sound like failing hardware. The archives are littered with examples of people who swore black and blue that failing hardware could not possibly be the cause of their mysterious reboots, until they found the failing hardware and replaced it :-) Check and swap out/replace RAM, power supply, CPU fan, cabling, CPU etc. Kris --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+ZWcZWry0BWjoQKURAmq1AJ9XI2BhrkMoTwYdfUl+tEu0SbTJgQCg+U/a xe0WGPYwu8zkTkbRT6aqHzo= =2+6X -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message