Date: Fri, 23 Mar 2001 21:16:38 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: The Hermit Hacker <scrappy@hub.org> Cc: freebsd-current@FreeBSD.org Subject: RE: spin lock panic ... Message-ID: <XFMail.010323211638.jhb@FreeBSD.org> In-Reply-To: <Pine.BSF.4.33.0103232326260.41105-100000@mobile.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24-Mar-01 The Hermit Hacker wrote:
> On Fri, 23 Mar 2001, John Baldwin wrote:
>
>>
>> On 24-Mar-01 The Hermit Hacker wrote:
>> >
>> > Over the past few days, I reformatted my computer clean, installed
>> > 4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel
>> > and world ... went to ports/x11/XFree86-4 and did a 'make install' ...
>> > after awhile, it panic'd as below:
>> >
>> > panic: spin lock sched lock held by 0xcb332840 for > 5 seconds
>> > cpuid = 1; lapic.id = 01000000
>> > Debugger("panic")
>> >
>> > CPU1 stopping CPUs: 0x00000001... stopped.
>> >
>> > Now, I do have DDB enabled in the kernel ... but, for the life of me, I
>> > can't seem to find any docs on the keystroke required to drop into it :(
>> > 'man ddb' doesn't document it that I can find, nor does LINT ...
>>
>> Uhh, if it panic'd, it should already be in ddb at a db> prompt assuming you
>> have DDB in your kernel.
>
> didn't ... last line was as above ... I've even tested my DDB to make sure
> I can get to the db> prompt after alfred reminded me of the ctl-alt-esc to
> get there, and it works ...
Well, that meants it most likely deadlocked trying to get into the debugger. I
haven't seen any deadlocks like this in months though.
--
John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010323211638.jhb>