ntime, maybe the message will give someone a
>> clue:
>>
>> panic: spin lock sched lock held by 0xca462390 for > 5 seconds
>> cpuid = 0; lapic.id =
>> Debugger("panic")
>
> If this is reproduceable, you might try setting 'debug.trace_on_p
On Thu, 31 Jul 2003, Lars Eggert wrote:
> got this panic overnight. Machine was wedged solid and didn't enter ddb
> after the panic. I'll recompile with verbose diagnostics and see if it
> happens again. In the meantime, maybe the message will give someone a
> clue:
>
Hi,
got this panic overnight. Machine was wedged solid and didn't enter ddb
after the panic. I'll recompile with verbose diagnostics and see if it
happens again. In the meantime, maybe the message will give someone a clue:
panic: spin lock sched lock held by 0xca462390 for > 5
just panic'd, couldn't even get to the ddb prompt this time ...
panic: spin lock sched lock held by 0xcb34b840 for > 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs ...
Marc G. Fournier ICQ#7615664 IR
