VFS: panic: lockmgr: locking against myself (msdosfs)

From: Alexander Leidinger <Alexander_at_Leidinger.net>
Date: Sun, 19 Jun 2005 13:46:14 +0200
Hi,

I've got this panic:
---snip---
panic: lockmgr: locking against myself
KDB: enter: panic
[thread pid 683 tid 100140 ]
Stopped at      kdb_enter+0x2a: leave   
db> bt
No such command
db> trace
Tracing pid 683 tid 100140 td 0xc187f780
kdb_enter(c059ce0f) at kdb_enter+0x2a
panic(c059b86a,80,c187f780,0,c05c8300) at panic+0xa9
lockmgr(c206b9e8,2002,c206ba0c,c187f780,d0a398c8) at lockmgr+0x44e
vop_stdlock(d0a398e8,2,c206b990,d0a39904,c04df46e) at vop_stdlock+0x1e
VOP_LOCK_APV(c05bc480) at VOP_LOCK_APV+0x30
vn_lock(c206b990,2002,c187f780) at vn_lock+0xa3
vget(c206b990,2002,c187f780) at vget+0x8d
vfs_hash_get(c17e9800,c000,2,c187f780,d0a39994,c04632dc,d0a39998) at vfs_hash_get+0x87
deget(c1763d00,40003,0,d0a39a08) at deget+0x69
msdosfs_lookup(d0a39a80,d0a39abc,c04cdc22,c05bc480,d0a39a80) at msdosfs_lookup+0x6a8
VOP_CACHEDLOOKUP_APV(c05bc480,d0a39a80,c187f780,c2080200,c05de840) at VOP_CACHEDLOOKUP_APV+0x27
vfs_cache_lookup(d0a39b1c,c206b990,d0a39bc4,d0a39b38,c04d0d98) at vfs_cache_lookup+0xae
VOP_LOOKUP_APV(c05bc480) at VOP_LOOKUP_APV+0x30
lookup(d0a39b9c,0,d0a39bc4,0,3f800000) at lookup+0x38b
namei(d0a39b9c,84a6340,0,0,c177cbb0) at namei+0x2cb
kern_lstat(c187f780,84a6340,0,d0a39c70) at kern_lstat+0x47
lstat(c187f780) at lstat+0x1b
syscall(3b,3b,3b,bf6fbe30,84a6340) at syscall+0x207
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (190, FreeBSD ELF32, lstat), eip = 0x28ddc75f, esp = 0xbf6fbd4c, ebp = 0xbf6fbdf8 ---
---snip---

This is with -current as of yesterday. Do you need more information?

Bye,
Alexander.

-- 
                   It's not a bug, it's tradition!

http://www.Leidinger.net                       Alexander _at_ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7
Received on Sun Jun 19 2005 - 09:45:48 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:37 UTC