DragonFly BSD
DragonFly bugs List (threaded) for 2009-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [issue1634] panic: spin_lock: 0xe4ad1320, indefinitive wait!

From: Antonio Huete Jimenez <ahuete.devel@xxxxxxxxx>
Date: Wed, 23 Dec 2009 12:36:42 +0100

Hi Petr,

As far as I know you don't have to recompile with DDB_UNATTENDED, just
change the sysctl debug.debugger_on_panic to 0.
Note that you need to have a correctly set dumpdev (which the
installer sets now in 7etc/rc.conf to your swap device) in order to
get the dumps.

With that, once you get a panic, there will be a dump and the machine
should be restarted without intervention.

Antonio Huete

2009/12/23  <elekktretterr@exemail.com.au>:
>> Petr,
>> I guess you have dumpdev configured in the server, no? Since first of
>> december we got minidumps that will produce quite small dumps despite
>> the memory you have on the machine. You will find the cores on
>> /var/crash as usual, so next time maybe we can catch the panic :)
> There is no keyboard permanently attached to the server though. If it
> panics, I need to plugin one, but then I cant type in the ddb screen so I
> can only press the reset button. Which is why I was asking, is there any
> way to automate this? ie. 1) System panics and gets into DDB, 2) a dump is
> automatically created 3) System automatically reboots.
> I've been notified there is DDB_UNATTENDED kernel option, but will this
> create a dump before rebooting?
> Petr

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]