Date: Mon, 04 Aug 2003 16:36:48 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Robert Watson <rwatson@freebsd.org> Cc: current@freebsd.org Subject: Re: panic: spin lock sched lock held Message-ID: <XFMail.20030804163648.jhb@FreeBSD.org> In-Reply-To: <Pine.NEB.3.96L.1030731160243.37179E-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20030804163648.jhb>