From owner-freebsd-stable Sat Dec 19 23:52:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14606 for freebsd-stable-outgoing; Sat, 19 Dec 1998 23:52:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14601 for ; Sat, 19 Dec 1998 23:52:02 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zrdeR-0001nt-00; Sat, 19 Dec 1998 23:51:43 -0800 Date: Sat, 19 Dec 1998 23:51:39 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Staffan Ulfberg cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic In-Reply-To: <873e6b1r3b.fsf@multivac.fatburen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Dec 1998, Staffan Ulfberg wrote: > I sort of think that a kernel panic is a bug, regardless of the level > of stupidity needed to trigger it. Any comments? Well, basically you corrupted your filesystems. Corrupted filesystems cause panics. It isn't a bug. Panics are the only recourse. What else could the kernel do? The filesystem is unintelligble. The safest thing is to panic, which should cause a reboot and perhaps will be better next time around. > Staffan Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message