From owner-freebsd-current Fri Mar 24 11:35:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA17563 for current-outgoing; Fri, 24 Mar 1995 11:35:14 -0800 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA17556 for ; Fri, 24 Mar 1995 11:35:12 -0800 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id NAA03010; Fri, 24 Mar 1995 13:34:53 -0600 Received: by olympus (4.1/TSS2.1) id AA27636; Fri, 24 Mar 95 13:33:26 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9503241933.AA27636@olympus> Subject: Boom! kernel go panic on BOOT. To: bde@zeta.org.au (Bruce Evans) Date: Fri, 24 Mar 1995 13:33:25 -0600 (CST) Cc: current@FreeBSD.org In-Reply-To: <199503240957.TAA12675@godzilla.zeta.org.au> from "Bruce Evans" at Mar 24, 95 07:57:58 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 582 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce, 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? Thanks Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________