Date: Tue, 4 Mar 2003 18:55:21 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Bsd Neophyte <bsdneophyte@yahoo.com> Cc: Tuc <tuc@ttsg.com>, freebsd-questions@FreeBSD.ORG Subject: Re: still can't resolve these system reboots... help please Message-ID: <20030305025521.GA94920@rot13.obsecurity.org> In-Reply-To: <20030304233008.40599.qmail@web20109.mail.yahoo.com> References: <200303041302.h24D2erk009815@himinbjorg.ttsg.com> <20030304233008.40599.qmail@web20109.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030305025521.GA94920>