Date: Fri, 27 Apr 2007 09:24:02 +0800 From: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> To: freebsd-current@freebsd.org Subject: Re: Panic on boot. How do I get a kernel dump. Message-ID: <20070427012401.GZ2445@obelix.dsto.defence.gov.au> In-Reply-To: <de193d070704261535k11e5de1eh12842a4ab340a971@mail.gmail.com> References: <de193d070704231144o40426f86j263e2309e2f9490f@mail.gmail.com> <f0j274$1bu$1@sea.gmane.org> <de193d070704231519h671193emdd5f8673246559ad@mail.gmail.com> <20070426204602.GA81382@keltia.freenix.fr> <de193d070704261535k11e5de1eh12842a4ab340a971@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
-aW
IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070427012401.GZ2445>