From owner-freebsd-current@FreeBSD.ORG  Fri Apr 27 01:30:36 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id BC55316A402
	for <freebsd-current@freebsd.org>; Fri, 27 Apr 2007 01:30:36 +0000 (UTC)
	(envelope-from anderson@freebsd.org)
Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50])
	by mx1.freebsd.org (Postfix) with ESMTP id 8F4E613C487
	for <freebsd-current@freebsd.org>; Fri, 27 Apr 2007 01:30:36 +0000 (UTC)
	(envelope-from anderson@freebsd.org)
Received: from neutrino.centtech.com (andersonbox1.centtech.com
	[192.168.42.21])
	by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l3R1UZl2085919
	for <freebsd-current@freebsd.org>; Thu, 26 Apr 2007 20:30:36 -0500 (CDT)
	(envelope-from anderson@freebsd.org)
Message-ID: <4631523C.3030301@freebsd.org>
Date: Thu, 26 Apr 2007 20:30:36 -0500
From: Eric Anderson <anderson@freebsd.org>
User-Agent: Thunderbird 2.0.0.0 (X11/20070420)
MIME-Version: 1.0
To: freebsd-current@freebsd.org
References: <de193d070704231144o40426f86j263e2309e2f9490f@mail.gmail.com>
	<f0j274$1bu$1@sea.gmane.org>
	<de193d070704231519h671193emdd5f8673246559ad@mail.gmail.com>
	<20070426204602.GA81382@keltia.freenix.fr>
	<de193d070704261535k11e5de1eh12842a4ab340a971@mail.gmail.com>
	<20070427012401.GZ2445@obelix.dsto.defence.gov.au>
In-Reply-To: <20070427012401.GZ2445@obelix.dsto.defence.gov.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.4/3165/Thu Apr 26 08:03:24 2007 on
	mh1.centtech.com
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.6
X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com
Subject: Re: Panic on boot. How do I get a kernel dump.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Apr 2007 01:30:36 -0000

On 04/26/07 20:24, Wilkinson, Alex wrote:
>     0n Thu, Apr 26, 2007 at 03:35:15PM -0700, Tom Cumming wrote: 
> 
>     >>What about using the "panic" command in ddb? :)
>     >
>     >
>     >The problem is not getting it to panic, the problem is getting it to save
>     >core after the panic. I can find no way to configure the dump device before
>     >I boot, only after the OS is up. This means a panic during boot will not
>     >dump core because the dump device is not configured.
> 
> Boot off of a good kernel and:
> 
>    # boot -s
>    # fsck -p
>    # mount /var
>    # savecore /kernel.broken /var/crash


Does this make any sense?

I think what Tom was trying to say was that while the kernel is booting, 
say right at root mount time, there is no dump device set, so the kernel 
doesn't know where to dump the dump when a 'call doadump' is initiated.

I think what he (and others) want to know is: how to set the dump device 
at the loader prompt so you can get a crash dump before the dump device 
normally would get set up in /etc/rc.d/dumpon


Eric