hi,
sporadically, I see this:
lockmgr: thread 0xffffff0004a8b390 unlocking unheld lock
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_lockmgr() at _lockmgr+0x6ae
VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
unionfs_unlock() at unionfs_unlock+0x22f
VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
vn_read() at vn_read+0x264
dofileread() at dofileread+0xa1
kern_readv() at kern_readv+0x4c
read() at read+0x54
syscall() at syscall+0x256
Xfast_syscall() at Xfast_syscall+0xab
--- syscall (3, FreeBSD ELF64, read), rip = 0x8017545bc, rsp = 0x7fffffffaf98,
rbp = 0x7fffffffb025 ---
sf-02> zgrep 'unlocking unheld lock' /var/log/messages*
/var/log/messages:May 25 03:03:37 sf-02 kernel: lockmgr: thread
0xffffff0004ed0720 unlocking unheld lock
/var/log/messages:May 31 03:03:10 sf-02 kernel: lockmgr: thread
0xffffff0004ed6ab0 unlocking unheld lock
/var/log/messages:Jun 10 03:03:19 sf-02 kernel: lockmgr: thread
0xffffff0004a8b390 unlocking unheld lock
it happens around 3 am, so I guess it must be some daily script that trips
this.
danny
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
