From owner-freebsd-current@FreeBSD.ORG Mon Mar 6 15:41:39 2006 Return-Path: X-Original-To: current@freebsd.org 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 973DA16A425 for ; Mon, 6 Mar 2006 15:41:39 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54CEC43D6D for ; Mon, 6 Mar 2006 15:41:27 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k26FfKxK018384; Mon, 6 Mar 2006 10:41:24 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Kris Kennaway Date: Fri, 3 Mar 2006 16:20:08 -0500 User-Agent: KMail/1.9.1 References: <20060302235957.GA75453@xor.obsecurity.org> <200603031114.48956.jhb@freebsd.org> <20060303210317.GB11807@xor.obsecurity.org> In-Reply-To: <20060303210317.GB11807@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603031620.10560.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1315/Sun Mar 5 05:31:57 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED,AWL autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: current@freebsd.org Subject: Re: panic: blockable sleep lock (sleep mutex) Giant @ kern/kern_intr.c:661 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Mar 2006 15:41:40 -0000 On Friday 03 March 2006 16:03, Kris Kennaway wrote: > On Fri, Mar 03, 2006 at 11:14:47AM -0500, John Baldwin wrote: > > On Thursday 02 March 2006 18:59, Kris Kennaway wrote: > > > Updated to -current, panicked at boot: > > > > > > Timecounters tick evpanic: blockable sleep lock (sleep mutex) Giant @ kern/kern_intr.c:661 > > > cpuid = 0 > > > KDB: enter: panic > > > [thread pid 30 tid 100035 ] > > > Stopped at kdb_enter+0x30: leave > > > db> wh > > > Tracing pid 30 tid 100035 td 0xcc5b7bd0 > > > kdb_enter(c072c0f6,0,c07303fc,f5893c50,cc5b7bd0) at kdb_enter+0x30 > > > panic(c07303fc,c074362d,c073e0e1,c07294ca,295) at panic+0x13f > > > witness_checkorder(c07939e8,9,c07294ca,295,c07999f8) at witness_checkorder+0xd6 > > > _mtx_lock_flags(c07939e8,0,c07294c1,295,2) at _mtx_lock_flags+0x94 > > > ithread_execute_handlers(cc5c1000,cc5f8c80,c052b648,c07939d0,cc5b7bd0) at ithread_execute_handlers+0x10c > > > ithread_loop(cc5d3440,f5893d38,c07292b7,31a,cc5d3440) at ithread_loop+0x78 > > > fork_exit(c051d959,cc5d3440,f5893d38) at fork_exit+0xc5 > > > fork_trampoline() at fork_trampoline+0x8 > > > --- trap 0x1, eip = 0, esp = 0xf5893d6c, ebp = 0 --- > > > > Something has leaked a critical section. Do you have witness_skipspin enabled? > > Can you try turning it off? It's probably a missing unlock of a spin mutex > > somewhere. > > WITNESS_SKIPSPIN was not enabled. Well, the panic means td_critnest > 1, so a critical section leaked somewhere. The box must have been really slow if you had witness checking spin mutexes. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org