From owner-freebsd-stable Fri May 7 13:24:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2378D154EC for ; Fri, 7 May 1999 13:24:35 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from graves.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 May 99 21:24:35 +0100 (BST) To: Mike Smith Cc: freebsd-stable@freebsd.org Subject: Re: Strange reboot saga In-reply-to: Your message of "Fri, 07 May 1999 11:55:29 PDT." <199905071855.LAA01003@dingo.cdrom.com> X-Request-Do: Date: Fri, 07 May 1999 21:24:34 +0100 From: David Malone Message-ID: <9905072124.aa14244@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A totally spontaneous reboot, with absolutely no console output > whatsoever is almost certainly a hardware problem. FreeBSD _will_not_ > reboot without telling you about it; in some extreme cases you will get > a very terse message (usually indicating kernel stack overflow) but you > will _always_ get something. > > So if you're rebooting with _no_ console output at all, look to your > hardware. To be fair though - it can be very easy to miss these messages. If X is running you don't stand a chance and if its a page fault there is no evidence left in the log files either. Deadlocks don't produce any messages by their very nature ;-) Would it be possible to dump the page fault info somewhere it can be got back again? I know the kernel is probably messed up if you've hit a page fault, but it can't be than much worse than trying to sync disks after a panic. Atleast you might get a log message then. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message