Re: Panic with recursed on non-recursive lock
On 23-Sep-01 Munehiro Matsuda wrote: Hi all, Here's another one from src-cur.4972.gz. It's repeatable. --- # ps -ae lock order reversal 1st 0xc7fe4d08 process lock @ ../../../kern/kern_proc.c:215 2nd 0xc03e6620 Giant @ ../../../kern/subr_trap.c:98 exclusive (sleep mutex) process lock (0xc7fe4d08) locked @ ../../../kern/kern_proc.c:215 panic: system call open returning with mutex(s) held Something is not unlocking the process after pfind(). A trace here at the point of the reversal might help. Please turn on WITNESS_DDB. Debugger(panic) Stopped atDebugger+0x44: pushl%ebx db t Debugger(c0322ffb) at Debugger+0x44 panic(c0345de0,c0327489,bfbfe574,10,bfb0) at panic+0x70 syscall(2f,2f,2f,bfb0,10) at syscall+0x602 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (1, FreeBSD ELF, sys_exit), eip = 0x804f404, esp = 0xbfbfe538, ebp = 0xbfbe974 --- db --- Also, newest kernel (from src-cur.4973.gz) panics on boot. --- Mounting root from ufs:/dev/ad0s2a panic: lock (sleep mutex) vnode interlock not locked @ ../../../kern/vfs_default.c:460 Debugger(panic) Stopped atDebugger+0x44: pushl%ebx db t Debugger(c0321e3b) at Debugger+0x44 panic(c0324e00,c0320e60,c0328ffc,c0328990,1cc) at panic+0x70 witness_unlock(c85e3f2c,8,c0328980,1cc,c85e3f2c,1,c0320e77,f6) at witness_unlock+0x1d0 _mtx_unlock_flags(c85e3f2c,0,c0328980,1cc,c04d0bd0) at _mtx_unlock_flags+0x59 vop_nolock(c04d0be8,c04d0bf8,c021fd56,c04d0be8,c04d0d4c) at vop_nolock+0x24 vop_defaultop(c04d0be8) at vop_defaultop+0x15 vn_lock(c85e3ec0,20002,c03e01e4,c04d0d4c,c1405780) at vn_lock+0xca ffs_mountfs(c85e3ec0,c1406200,c03e01e4,c0388140,c04d0d4c) at ffs_mountfs+0x7e ffs_mount(c1406200,0,0,0,c03e01e4) at ffs_mount+0x67 vfs_mountroot_try(c04ad52d,c032858c) at vfs_mountroot_try+0x14e vfs_mountroot(0,4cdc00,4cd000,0,c012881c) at vfs_mountroot+0x5a mi_startup() at mi_startup+0x90 begin() at begin+0x43 db --- Ugh, not sure what is causing this. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic with recursed on non-recursive lock
On 23 Sep, Munehiro Matsuda wrote: Hi, I got following panic with recent -current (src-cur.4972.gz): recursed on non-recursive lock (sleep mutex) process lock @ ../../../i386/i386/trap.c:807 first acquired @ ../../../kern/subr_trap.c:100 panic: recurse syncing disks... panic: bremfree: bp 0xc3bbd5ec not locked System rebooted automatically, so I couldn't get any traces... :-( Has anybody seen this before? Sort of (-current archive), at least the bremfree part: - Message-ID: [EMAIL PROTECTED] - Message-ID: [EMAIL PROTECTED] Bye, Alexander. -- The three Rs of Microsoft support: Retry, Reboot, Reinstall. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic with recursed on non-recursive lock
Hi all, Here's another one from src-cur.4972.gz. It's repeatable. --- # ps -ae lock order reversal 1st 0xc7fe4d08 process lock @ ../../../kern/kern_proc.c:215 2nd 0xc03e6620 Giant @ ../../../kern/subr_trap.c:98 exclusive (sleep mutex) process lock (0xc7fe4d08) locked @ ../../../kern/kern_proc.c:215 panic: system call open returning with mutex(s) held Debugger(panic) Stopped at Debugger+0x44: pushl%ebx db t Debugger(c0322ffb) at Debugger+0x44 panic(c0345de0,c0327489,bfbfe574,10,bfb0) at panic+0x70 syscall(2f,2f,2f,bfb0,10) at syscall+0x602 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (1, FreeBSD ELF, sys_exit), eip = 0x804f404, esp = 0xbfbfe538, ebp = 0xbfbe974 --- db --- Also, newest kernel (from src-cur.4973.gz) panics on boot. --- Mounting root from ufs:/dev/ad0s2a panic: lock (sleep mutex) vnode interlock not locked @ ../../../kern/vfs_default.c:460 Debugger(panic) Stopped at Debugger+0x44: pushl%ebx db t Debugger(c0321e3b) at Debugger+0x44 panic(c0324e00,c0320e60,c0328ffc,c0328990,1cc) at panic+0x70 witness_unlock(c85e3f2c,8,c0328980,1cc,c85e3f2c,1,c0320e77,f6) at witness_unlock+0x1d0 _mtx_unlock_flags(c85e3f2c,0,c0328980,1cc,c04d0bd0) at _mtx_unlock_flags+0x59 vop_nolock(c04d0be8,c04d0bf8,c021fd56,c04d0be8,c04d0d4c) at vop_nolock+0x24 vop_defaultop(c04d0be8) at vop_defaultop+0x15 vn_lock(c85e3ec0,20002,c03e01e4,c04d0d4c,c1405780) at vn_lock+0xca ffs_mountfs(c85e3ec0,c1406200,c03e01e4,c0388140,c04d0d4c) at ffs_mountfs+0x7e ffs_mount(c1406200,0,0,0,c03e01e4) at ffs_mount+0x67 vfs_mountroot_try(c04ad52d,c032858c) at vfs_mountroot_try+0x14e vfs_mountroot(0,4cdc00,4cd000,0,c012881c) at vfs_mountroot+0x5a mi_startup() at mi_startup+0x90 begin() at begin+0x43 db --- Hope this helps, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
