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

Re: DFly-stable as of April 1st crashed, but no crash dump was possible due to ips driver being unable to do crash dumps

To: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
From: Raphael Marmier <raphael@xxxxxxxxxxx>
Date: Sun, 03 Apr 2005 14:47:44 +0200

Matthew Dillon wrote:
:Raphael Marmier wrote:
:> Joerg Sonnenberger wrote:
:> :>> On Sat, Apr 02, 2005 at 07:04:30PM +0200, Raphael Marmier wrote:
:>>> I am unable to get a crash dump through the ddb and typing panic and :>>> hitting enter twice. I end up in the same state as you discribe.
:>>> hint anyone?
:>> What interrupt masks does it show?
:> :> :> I since just hacked syscons.c so panic() is called in place of :> Debugger() when I hit cntl-alt-esc.
:> The aforementionned problem doesn't happen and it goes past the 'syncing :> disks ...', then when I type continue, it does (eureka!) save core.
:> :> I will now restore my kernel to the normal state in order to really :> answer your question.
:> :> Raphael
:I don't see what this interrupt mask is. The closest I see is about an :intr_mux(...) at intr_mux+0x21
:What happens is that I get "syncing disks ... " Then every 5-10 seconds :a "CHKTOKEN loop 0" message, forever.

You should only need to 'sysctl kern.sync_on_panic=0' for it to be
able to get past the syncing disks code.

Ack, but what I meant is that syncing actually _works_ with the direct panic() call in syscons.c in place of Debugger(). And I get the dump.

So it looks like there is an issue with DBB and syncing, as syncing fails when use together with DDB. Isn't it?

This is without using the serial console.


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