Re: Autodumping on panic

From: Jeremie Le Hen <jeremie_at_le-hen.org>
Date: Sun, 4 Mar 2007 21:38:02 +0100
Hi, Eric,

On Sun, Mar 04, 2007 at 02:21:54PM -0600, Eric Anderson wrote:
> On 03/02/07 15:04, Jeremie Le Hen wrote:
> >I've just changed my window manager, and I'm experiencing a few issues
> >with it.  This may be a panic but I can't be sure for now.  Indeed I
> >don't have a serial port on my laptop.
> >
> >I'm sure it is possible to ask the kernel to call doadump()
> >automatically on panic, but I can't remember how.  Please, could you
> >give me the correct way to do it ?
> 
> 
> Any word on this?  I'd love to set this up too.  Would be nice to 
> auto-dump+reset on servers..

Robert Watson replied me privately.  Hereafter you will find my reply:

On Sat, Mar 03, 2007 at 03:12:53PM +0100, Jeremie Le Hen wrote:
> On Sat, Mar 03, 2007 at 12:35:43PM +0000, Robert Watson wrote:
> > You may be able to set the "unattended" sysctl or kernel compile option to 
> > cause it to panic and reboot rather than dropping into DDB.  However, I'm 
> > not in front of a box I can test that on right now, so I'm replying 
> > privately in case I'm completely wrong :-).
> 
> Thank you for your reply.  I've checked the code in kern_shutdown.c and
> indeed KDB_UNATTENDED sets the default value of debug.debugger_on_panic
> to 0.  In case we didn't drop to the debugger, doadump() is called,
> this is what I want.  Actually turning off the sysctl manually should
> also do it.

I hope this wille help.

Regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >
Received on Sun Mar 04 2007 - 19:36:17 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:06 UTC