Re: lockmgr: locking against myself

[Andre Nathan <andre@xxxxxxxxxxxx>]

On Mon, 15 Nov 2004, Andre Nathan wrote:

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

Reproduced it today, this time with with dumpdev enabled. The dumps are
at

http://leaf.dragonflybsd.org/~andre/kernel.0.bz2  and
http://leaf.dragonflybsd.org/~andre/vmcore.0.bz2

Here's the new trace:

panic: lockmgr: locking against myself
panic: (10000002, 10000000, 0, cc89a98f, c0257a91) at panic+0x84
panic: (c04650a0, c7b6b278, 2, 10000002, cc668b6c) at panic+0x84
lockmgr(ccc94f0c, 10000002, 0, c5502020, cc89aa1c) at lockmgr+0x2c1
vop_stdlock(cc89aa2c, cc89aa50, c029e4d8, cc89aa2c, cc668af8) at vop_stdlock+0x1a
ufs_vnoperate(cc89aa2c, cc668af8, c04f0240, c7b6b278, 1) at ufs_vnoperate+0x16
vop_lock(c7b6b278, cc668af8, 10000002, c5502020) at vop_lock+0x68
vn_lock(cc668af8, cc5502020, c7b6b278, cc6231a8) at vn_lock+0x22
ext2_link(cc89aab0, fffffffe, c04f0000, c7b6b278, 2) at ext2_link+0x45
vop_link(c7b6b278, cc668a18, cc668af8, cc89ab00, c7b6b278) at vop_link+0x68
vop_compat_nlink(cc89ab48, cc89ab38, c038e686, cc89ab48, cc89ab6c) at vop_compat_nlink+0x11b
vop_defaultop(cc89ab48, cc89ab6c, c029f134, cc82ab48, 0) at vop_defaultop+0x16
ufs_vnoperate(cc89ab48, 0, c04f0860, c7b6b278, cc623118) at ufs_vnoperate+0x16
vop_nlink(c7b6b278, cc6231a8, cc668af8, c0d09268, 0) at vop_nlink+0x68
kern_link(cc89abd8, cc89abb0, 0, c4e6c700, 2) at kern_link+0xe3
link(cc89ac34, 805b320, 805d140, 805b320, cc89ad20) 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


Andre