From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 07:59:00 2004 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 97E8216A4CF for ; Thu, 29 Jan 2004 07:59:00 -0800 (PST) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D54743D5E for ; Thu, 29 Jan 2004 07:58:49 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 8269 invoked from network); 29 Jan 2004 15:58:47 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 29 Jan 2004 15:58:47 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i0TFwIM6069201; Thu, 29 Jan 2004 10:58:37 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Peter Losher , current@freebsd.org Date: Thu, 29 Jan 2004 10:48:20 -0500 User-Agent: KMail/1.5.4 References: <20040127082106.L14045@farside.isc.org> <200401281850.08627.Peter_Losher@isc.org> <200401290206.36852.Peter_Losher@isc.org> In-Reply-To: <200401290206.36852.Peter_Losher@isc.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401291048.20599.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: spin lock panic in 5.2-REL (more info) 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: Thu, 29 Jan 2004 15:59:00 -0000 On Thursday 29 January 2004 05:06 am, Peter Losher wrote: > login: spin lock sched lock held by 0x8d2f7a00 for > 5 seconds > panic: spin lock held too long > cpuid = 4; > Debugger("panic") > Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 > db> trace > Debugger(80857eb0,4,808577cc,f6a46bd4,100) at Debugger+0x55 > panic(808577cc,80857891,8d2f7a00,80910ee0,8726ad80) at panic+0x156 > _mtx_lock_spin(80910ee0,0,8085636e,18d,8d2f7b40) at _mtx_lock_spin+0x9f > _mtx_lock_spin_flags(80910ee0,0,8085636e,18d,4) at > _mtx_lock_spin_flags+0x60 > ithread_schedule(8726ad80,1,f6a46c70,1c,8726ca00) at > ithread_schedule+0xae > intr_execute_handlers(8d2d0f4c,f6a46c74,f6a46cb8,807d84e3,4c) at > intr_execute_handlers+0xe9 > lapic_handle_intr(4c) at lapic_handle_intr+0x3a > Xapic_isr2() at Xapic_isr2+0x33 > --- interrupt, eip = 0x80a2fef5, esp = 0xf6a46cb8, ebp = 0xf6a46cb8 --- > acpi_cpu_c1(1,1,0,b6e31890,246) at acpi_cpu_c1+0x5 > acpi_cpu_idle(f6a46d10,806251f8,80910ee0,0,8085631b) at > acpi_cpu_idle+0xd5 > cpu_idle(80910ee0,0,8085631b,5c,8726b710) at cpu_idle+0x28 > idle_proc(0,f6a46d48,8085621f,311,0) at idle_proc+0x18 > fork_exit(806251e0,0,f6a46d48) at fork_exit+0x7e > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xf6a46d7c, ebp = 0 --- Can you use show pcpu to find what threads are executing on other CPUs and get traces of those threads via 'tr '? We need to figure out where sched_lock is being held so long. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org