panic: lockmgr on FreeBSD 7.0-RELEASE-p4 amd64

[John Baldwin]

On Wednesday 24 September 2008 12:17:56 pm Jeff Wheelhouse wrote:
> 
> We got the same panic again, this time after switching to the ULE  
> scheduler:
> 
> panic: lockmgr: thread 0xffffff0050858350, not exclusive lock holder  
> 0xffffff00074959f0 unlocking
> cpuid = 0
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
> panic() at panic+0x17a
> _lockmgr() at _lockmgr+0x872
> VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
> null_unlock() at null_unlock+0xff
> VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
> nullfs_mount() at nullfs_mount+0x244
> vfs_donmount() at vfs_donmount+0xe4d
> nmount() at nmount+0xa5
> syscall() at syscall+0x254
> Xfast_syscall() at Xfast_syscall+0xab
> --- syscall (378, FreeBSD ELF64, nmount), rip = 0x206845ac, rsp =  
> 0x7fffffffdfc8, rbp = 0x7fffffffdfd0 ---

Can you use gdb or the like to get the souce file/line for the 
nullfs_mount+0x244 frame?

i.e. 'gdb /boot/kernel/kernel'

(gdb) l *nullfs_mount+0x244

-- 
John Baldwin