Date: Wed, 19 May 2004 18:04:31 +0300 From: Nick Strebkov <nick@humgat.org> To: Peter Pentchev <roam@ringlet.net> Cc: hackers@freebsd.org Subject: Re: obtaining a kernel crash dump Message-ID: <20040519145945.GA3821@temp.interexc.com> In-Reply-To: <20040519142004.GA5125@straylight.m.ringlet.net> References: <20040519133442.GA90053@nord.interexc.com> <20040519142004.GA5125@straylight.m.ringlet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 19, 2004 at 05:20:04PM +0300, Peter Pentchev wrote: > On Wed, May 19, 2004 at 04:34:42PM +0300, Nick Strebkov wrote: > > Hi there. > > > > I can't obtain a crash dump. > > > > % cat /sys/i386/conf/DEVEL | grep makeoptions > > makeoptions DEBUG=-g > > % cat /etc/rc.conf| grep dump > > dumpdev="/dev/ar0s1b" > > dumpdir="/var/crash" > > > > I'm testing my kernel patch and the following is what I see in > > /var/log/messages: > > Can you force the kernel to dump by using DDB? Place 'options DDB' in > your kernel config, then, when the system is quiescent, hit Ctrl-Alt-Esc > and type 'panic' at the DDB prompt. > > If this works, and you get a crash dump, then the problem might be that > with your kernel patch, the kernel is panicking in a low-level layer, > like memory management or disk drivers or something like that, and it > simply cannot make a crash dump, since that would mean invoking code > that depends on bad data or something. Thanks a lot. I'll try. I modify the ip_input.c in the manner like IPFW do. -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040519145945.GA3821>