panic: spin lock sched lock held

[Robert Watson]

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.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org      Network Associates Laboratories