Date: Fri, 21 May 1999 21:14:09 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: freebsd-hackers@FreeBSD.ORG, schimken@cs.rpi.edu, crossd@cs.rpi.edu Subject: Re: Repeatable kernel panic for 3.2-RELEASE NFS server Message-ID: <199905220414.VAA69868@apollo.backplane.com> References: <199905220338.XAA40251@cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:> entirely contained within the current stack trace.
:All my kernels are now DDB kernels :) But since I do almost all of
:my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing
:is not on the serial console server (sorry). I do have another question
:about DDB, I unstalled -STABLE as of today (from releng3.fre...) and I
:compiled the kernel with DDB, and DDB_UNATTENDED per usual. Now when I
:C-A-E to get into the debugger and type 'panic' it drops me at another
:debugging prompt. If I type panic from that I get the real thing, any ideas?
:
:My next email will hopefully have the stack trace for this panic.
:--
:David Cross | email: crossd@cs.rpi.edu
Panic has a counter. The first time it is called it tries to drop into the
debugger. The second time it is called it reboots the machine for real.
When you control-alt-escape, you have not yet called panic for the
first time, so when you panic manually from the DDB prompt it drops you
into the debugger again. Second time's the charm!
Since the debugger repeats the previous command if you just
hit return, I've gotten used to simply typing
'panic <return><return><return><return>...'
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905220414.VAA69868>