From owner-freebsd-questions@FreeBSD.ORG Sat Oct 8 23:20:23 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 826A816A41F for ; Sat, 8 Oct 2005 23:20:23 +0000 (GMT) (envelope-from garys@opusnet.com) Received: from opusnet.com (mail.opusnet.com [209.210.200.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3445C43D45 for ; Sat, 8 Oct 2005 23:20:23 +0000 (GMT) (envelope-from garys@opusnet.com) Received: from localhost.localhost [70.98.246.232] by opusnet.com with ESMTP (SMTPD32-8.05) id A431108D008C; Sat, 08 Oct 2005 16:20:17 -0700 Received: from localhost.localhost (localhost.localhost [127.0.0.1]) by localhost.localhost (8.13.3/8.13.3) with ESMTP id j98NOAor077938; Sat, 8 Oct 2005 16:24:10 -0700 (PDT) (envelope-from garys@opusnet.com) Received: (from jojo@localhost) by localhost.localhost (8.13.3/8.13.3/Submit) id j98NO4gU077937; Sat, 8 Oct 2005 16:24:04 -0700 (PDT) (envelope-from garys@opusnet.com) To: Paul Schmehl References: From: garys@opusnet.com (Gary W. Swearingen) Date: Sat, 08 Oct 2005 16:24:04 -0700 In-Reply-To: (Paul Schmehl's message of "Sat, 08 Oct 2005 15:51:25 -0500") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: What are the likely causes of reboots? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 23:20:23 -0000 Paul Schmehl writes: > What are the possible causes of spontaneous reboots? And what artifacts would be left behind that might indicate the I had an old EISA 486 do that several times a week when the external RAM cache went flakey. I don't recall the error logs, except a vague recollection that they gave no clue. The only way I determined the cause was because I could (and did) turn off that cache in the BIOS setup.