From owner-freebsd-current@FreeBSD.ORG Mon Aug 4 13:36:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0038A37B401 for ; Mon, 4 Aug 2003 13:36:31 -0700 (PDT) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7C8E43FBD for ; Mon, 4 Aug 2003 13:36:30 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1947 invoked from network); 4 Aug 2003 20:36:30 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 4 Aug 2003 20:36:30 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h74KaR9s018403; Mon, 4 Aug 2003 16:36:28 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 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: Mon, 04 Aug 2003 16:36:48 -0400 (EDT) From: John Baldwin To: Robert Watson cc: Lars Eggert cc: current@freebsd.org Subject: Re: panic: spin lock sched lock held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 20:36:32 -0000 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 <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/