From owner-freebsd-current Fri Mar 23 21:17:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 159DB37B71A for ; Fri, 23 Mar 2001 21:17:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2O5GRG36276; Fri, 23 Mar 2001 21:16:27 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 23 Mar 2001 21:16:38 -0800 (PST) From: John Baldwin To: The Hermit Hacker Subject: RE: spin lock panic ... Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- 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