Re: panic: spin lock sched lock held
On 31-Jul-2003 Robert Watson wrote:
> 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:
>>
>> 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_panic' so
> that you get an automatic trace even if you can't get into DDB. This
> might or might not work, but it's worth a try.
That only provides data on the second CPU, not the one holding hte lock
for too long (which is the one you actually care about)
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: spin lock sched lock held
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:
>
> 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_panic' so
that you get an automatic trace even if you can't get into DDB. This
might or might not work, but it's worth a try.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: spin lock sched lock held
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 seconds
cpuid = 0; lapic.id =
Debugger("panic")
Lars
--
Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute
smime.p7s
Description: S/MIME Cryptographic Signature
