From owner-freebsd-current Sat Mar 24 9:42:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.hub.org (SHW39-29.accesscable.net [24.138.39.29]) by hub.freebsd.org (Postfix) with ESMTP id 076CF37B719; Sat, 24 Mar 2001 09:42:18 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f2OHgGW07080; Sat, 24 Mar 2001 13:42:17 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Sat, 24 Mar 2001 13:42:16 -0400 (AST) From: The Hermit Hacker To: John Baldwin Cc: Subject: RE: spin lock panic ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Mar 2001, John Baldwin wrote: > > 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. I swear, my compuer is just sooooo special :) it hasn't happened since ... re started the X compile, it finished fine and installed .. *shrug* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message