From owner-freebsd-current Fri Mar 24 11:58:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA18131 for current-outgoing; Fri, 24 Mar 1995 11:58:24 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA18118 for ; Fri, 24 Mar 1995 11:58:16 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA31596; Sat, 25 Mar 1995 05:54:53 +1000 Date: Sat, 25 Mar 1995 05:54:53 +1000 From: Bruce Evans Message-Id: <199503241954.FAA31596@godzilla.zeta.org.au> To: bde@zeta.org.au, faulkner@mpd.tandem.com Subject: Re: Boom! kernel go panic on BOOT. Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >I tried the new kernel with the slice code. The kernel complained that >all my slices were bad. I don't think it liked any of them. Unfortunately >it panics before the boot msg is written to the log. Booting with a 3 day >old kernel works fine. >So, what information do you need or should I look at to figure out what >goes wrong and why? Send me the boot messages and output from fdisk on the boot disk and disklabel on the FreeBSD slice for the old kernel. Bruce