From owner-freebsd-stable Tue Feb 9 18:32:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22162 for freebsd-stable-outgoing; Tue, 9 Feb 1999 18:32:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22155 for ; Tue, 9 Feb 1999 18:32:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02049; Tue, 9 Feb 1999 18:27:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902100227.SAA02049@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Rahul Dhesi cc: freebsd-stable@FreeBSD.ORG Subject: Re: Spontaneous reboots In-reply-to: Your message of "Tue, 09 Feb 1999 18:26:06 PST." <199902100226.AA08300@waltz.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Feb 1999 18:27:36 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The next time the machine rebooted, I happened to have a video display > connected to it and I happened to be nearbuy, and I saw the error > message 'page fault in kernel mode" (or something similar). I had to > run elsewhere while this was going on, so I missed the display during > the filesystem sync and reboot that followed. Ack. The details associated with the pagefault in conjunction with your kernel would be critical in tracking this down. > BTW, SunOS does not require crash dumps to be enabled in order to find > out the reason for the crash. SunOS logs a kernel backtrace into > /var/log/messages after each panic. I don't think FreeBSD does. It > would be nice if the panic message and a stack dump could be saved > whether or not a full crash dump is being saved. FreeBSD tries to save the kernel message buffer over reboots, but your BIOS may be overwriting these. For obvious reasons, you can't expect to be able to write to the filesystem after a panic, and in some cases dumps can't be performed because the disk code is dead... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message