acquiring duplicate lock of same type: "vnode interlock"

Ariff Abdullah ariff at
Fri Mar 17 10:52:10 UTC 2006

I think I've read somewhere about panic during early root mount, fsck
etc.. Perhaps this might be related:

Full dmesg:

acquiring duplicate lock of same type: "vnode interlock"
 1st vnode interlock @ kern/vfs_vnops.c:791
 2nd vnode interlock @ kern/vfs_subr.c:2018
KDB: stack backtrace:
witness_checkorder() at witness_checkorder+0x4da
_mtx_lock_flags() at _mtx_lock_flags+0x4a
vrefcnt() at vrefcnt+0x31
null_checkvp() at null_checkvp+0x65
null_lock() at null_lock+0x5b
vn_lock() at vn_lock+0x6b
nullfs_root() at nullfs_root+0x4c
vfs_donmount() at vfs_donmount+0x1096
nmount() at nmount+0x82
syscall() at syscall+0x21b
Xfast_syscall() at Xfast_syscall+0xa8
--- syscall (378, FreeBSD ELF64, nmount), rip = 0x800679e8c, rsp =
0x7fffffffe558, rbp = 0x7fffffffee40 ---

Ariff Abdullah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the freebsd-stable mailing list