Re: panic: spin lock sched lock held

From: John Baldwin <jhb_at_FreeBSD.org>
Date: Mon, 04 Aug 2003 16:36:48 -0400 (EDT)
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 = 00000000
>> 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 <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
Received on Mon Aug 04 2003 - 11:36:32 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:17 UTC