Date: Thu, 31 Jul 2003 16:04:11 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Lars Eggert <larse@ISI.EDU> Cc: current@freebsd.org Subject: Re: panic: spin lock sched lock held Message-ID: <Pine.NEB.3.96L.1030731160243.37179E-100000@fledge.watson.org> In-Reply-To: <3F29410A.4040500@isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030731160243.37179E-100000>