From owner-freebsd-current Mon Nov 11 13:39: 2 2002 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 2C6C937B401 for ; Mon, 11 Nov 2002 13:39:01 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C26543E4A for ; Mon, 11 Nov 2002 13:39:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 29512 invoked from network); 11 Nov 2002 21:39:08 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2002 21:39:08 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id gABLcw2D002338; Mon, 11 Nov 2002 16:38:58 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20021111213427.GA74011@rot13.obsecurity.org> Date: Mon, 11 Nov 2002 16:39:00 -0500 (EST) From: John Baldwin To: Kris Kennaway Subject: RE: "panic: sleeping thread owns a mutex" in unmount() Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11-Nov-2002 Kris Kennaway wrote: > I just got this on a Nov 1 current kernel: > > panic: sleeping thread owns a mutex > Debugger("panic") > Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 > db> bt > No such command > db> trace > Debugger(c04038ad,c047e2c0,c0402a36,d928bb80,1) at Debugger+0x54 > panic(c0402a36,1,c04029a2,6b,0) at panic+0xab > propagate_priority(c6be8270,2,c04029a2,23b,c0401a58) at propagate_priority+0x13c > _mtx_lock_sleep(c044c420,0,c0409d2a,c47,0) at _mtx_lock_sleep+0x219 > _mtx_lock_flags(c044c420,0,c0409d2a,c47,15f) at _mtx_lock_flags+0x94 > vfs_msync(c5828c00,1,1,c6be8270,10000) at vfs_msync+0x5b > dounmount(c5828c00,80000,c6be8270,bfbffb06,0) at dounmount+0x123 > unmount(c6be8270,d928bd10,c04245ae,409,2) at unmount+0xcc > syscall(2f,2f,2f,809a40e,80b483d) at syscall+0x28e > Xint0x80_syscall() at Xint0x80_syscall+0x1d > --- syscall (22, FreeBSD ELF32, unmount), eip = 0x804b207, esp = 0xbfbff41c, ebp = 0xbfbff498 --- > db> > > Unfortunately I was unable to get a dump. If you use WITNESS (yes, it's slow) then you can find out when and where a thread went to sleep holding a lock which is much easier to try and backtrace. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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