From owner-freebsd-current Tue Nov 17 10:26:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20149 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:26:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20144 for ; Tue, 17 Nov 1998 10:26:41 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA05067; Tue, 17 Nov 1998 13:29:22 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 17 Nov 1998 13:29:22 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Damon Hopkins cc: Current Mailing list Subject: Re: Random rebooting In-Reply-To: <3651BF9B.A7D93857@rtci.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Damon Hopkins wrote: > Greg Lehey wrote: > > Not really. Your machine probably rebooted because of something like > > a panic, but you don't mention that. If you're running -CURRENT, you > > should at least have dumps enabled, and preferably a debug kernel so > > you can do something with the dumps. The only thing I can see from > > the messages you added was that you didn't have dumps enabled. > > I did not see a panic in any of the logs how do you expect the kernel to log a panic unless it's via a logged serial consol? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message