Date: Mon, 11 Nov 2002 16:39:00 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.org Subject: RE: "panic: sleeping thread owns a mutex" in unmount() Message-ID: <XFMail.20021111163900.jhb@FreeBSD.org> In-Reply-To: <20021111213427.GA74011@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20021111163900.jhb>