Re: Reproducible Panic with port iplog

From: Kris Kennaway <kris_at_FreeBSD.org>
Date: Tue, 8 Mar 2005 18:40:05 +0000
On Tue, Mar 08, 2005 at 10:09:01AM -0800, Doug White wrote:
> On Tue, 8 Mar 2005, Mike Jakubik wrote:
> 
> > Doug White said:
> >
> > >> Typing "call doadump" in the kernel debugger does work. Is there no way
> > >> to
> > >> have the kernel automatically do a dump when the system panics and there
> > >> is no debugger compiled in?
> > >
> > > That should be the default behavior if a dumpdev is set (in rc.conf with
> > > "dumpdev" or manually with the dumpon(8) command).
> >
> > It does not seem to be for me. The system just stands there doing nothing
> > after the panic, when there is no debugger built in the kernel.
> >
> > P.S. I have also submitted a PR for this.
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=78384
> 
> I don't know if I can get to this before the release, but I've put it on
> my tracking list.  I need a way to provoke a panic, and the best way seems
> to be to program the syscons panic key.

I've seen DDB_UNATTENDED cause a hang-on-panic instead of a dump +
reboot on HEAD.  I've also seen it not dumping core when it does
manage to reboot.  I haven't tested this on RELENG_5.

Kris
Received on Tue Mar 08 2005 - 17:40:05 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:29 UTC