lockmgr: locking against myself

Andre Nathan andre at rootshell.be
Mon Nov 15 18:57:57 PST 2004


Hello.

I got this panic with sources from today. My machine has two
ext2fs-mounted filesystems, which seem to be related. Trace follows:

panic: lockmgr: locking against myself
panic: (10000002, 10000000, 0, cc82a9f8, c0257a91) at panic+0x84
panic: (c04650a0, c7b6b278, 2, 10000002, ccc94f0c) at panic+0x84
lockmgr(ccc94f0c, 10000002, 0, c55021e0, cc82aa1c) at lockmgr+0x2c1
vop_stdlock(cc82aa2c, cc82aa50, c029e4d8, cc82aa2c, cc94e98) at vop_stdlock+0x1a
ufs_vnoperate(cc82aa2c, ccc94e98, c04f0240, c7b6b278, 1) at ufs_vnoperate+0x16
vop_lock(c7b6b278, ccc94e98, 10000002, c55021e0) at vop_lock+0x68
vn_lock(ccc94e98, c55021e0, c7b6b278, ccbabe00) at vn_lock+0x22
ext2_link(cc82aab0, fffffffe, c04f0000, c7b6b278, 2) at ext2_link+0x45
vop_link(c7b6b278, ccc953d8, ccc94e98, cc82ab00, c7b6b278) at vop_link+0x68
vop_compat_nlink(cc82ab48, cc82ab38, c038c686, cc82ab48, cc82ab6c) at vop_compat_nlink+0x11b
vop_defaultop(cc82ab48, cc82ab6c, c029f134, cc82ab48, 0) at vop_defaultop+0x16
ufs_vnoperate(cc82ab48, 0, c04f0860, c7b6b278, ccbaa858) at ufs_vnoperate+0x16
vop_nlink(c7b6b278, ccbabe00, ccc94e98, c0d08d28, 0) at vop_nlink+0x68
kern_link(cc82abd8, cc82abb0, 0, c4e6ca00, 2) at kern_link+0xe3
link(cc82ac34, 805b320, 805d140, 805b320, cc82ad20) at link+0x4b
syscall2(2f, 2f, 2f, 805b320, 805d140) at syscall2+0x246
Xint0x80_syscall() at Xint0x80_syscall+0x2a
Debugger("panic")
Stopped at      Debugger+0x34: movb $0, in_Debugger.357


Unfortunately I didn't have dumpdev enabled in rc.conf :(

Regards,
Andre





More information about the Bugs mailing list