Date: Sat, 17 Nov 2001 13:33:36 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Anthony Atkielski <anthony@atkielski.com> Cc: Kris Kennaway <kris@obsecurity.org>, FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Mysterious boot during the night Message-ID: <20011117133336.B88359@xor.obsecurity.org> In-Reply-To: <02a001c16f53$215323b0$0a00000a@atkielski.com>; from anthony@atkielski.com on Sat, Nov 17, 2001 at 11:32:10AM %2B0100 References: <020e01c16f42$14885c10$0a00000a@atkielski.com> <20011117015632.B87944@xor.obsecurity.org> <02a001c16f53$215323b0$0a00000a@atkielski.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Nov 17, 2001 at 11:32:10AM +0100, Anthony Atkielski wrote: > Agreed, but is there any place in the system where I mind find a clue as to the > type of failure encountered? In general there's no reliable way for failing hardware to report its failure mode correctly. e.g. run one of the memory testers in the ports collection to check for failing RAM, but remember that if the tester doesn't find a memory problem it doesn't mean you don't have one. Kris --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE79tewWry0BWjoQKURAhRLAJ9vBs/WZgrogQzxwH4IVRnHXHSPOQCg2bw5 UrKFRFvWLt7ZBnI+352EQmM= =dEot -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5-- 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?20011117133336.B88359>