panic: lockmgr: locking against myself

Mathieu Arnold mat at mat.cc
Mon Dec 19 06:27:07 PST 2005


Hi

just got that today :

Unread portion of the kernel message buffer:
panic: lockmgr: locking against myself
cpuid = 0
Uptime: 2d21h29m5s
Dumping 510 MB (2 chunks)
  chunk 0: 1MB (159 pages) ... ok
  chunk 1: 510MB (130416 pages) 494 478 462 446 430 414 398 382 366 350 334
318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14

#0  doadump () at pcpu.h:165
165     pcpu.h: No such file or directory.
        in pcpu.h
(kgdb) where
#0  doadump () at pcpu.h:165
#1  0xc04a03d3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2  0xc04a0784 in panic (fmt=0xc06305fb "lockmgr: locking against myself") at
/usr/src/sys/kern/kern_shutdown.c:555
#3  0xc04921b6 in lockmgr (lkp=0xc2ac27c8, flags=12290, interlkp=0x80,
td=0xc1ebd600) at /usr/src/sys/kern/kern_lock.c:330
#4  0xc04fc8e0 in vop_stdlock (ap=0x0) at /usr/src/sys/kern/vfs_default.c:258
#5  0xc0622557 in VOP_LOCK_APV (vop=0xc065d5a0, a=0xdeb59aa0) at
vnode_if.c:1642
#6  0xc0515b81 in vn_lock (vp=0xc2ac2770, flags=4098, td=0xc1ebd600) at
vnode_if.h:844
#7  0xc04fec97 in lookup (ndp=0xdeb59c0c) at
/usr/src/sys/kern/vfs_lookup.c:382
#8  0xc04fe8bd in namei (ndp=0xdeb59c0c) at /usr/src/sys/kern/vfs_lookup.c:203
#9  0xc0511059 in kern_rename (td=0xc1ebd600, from=0x0, to=0x0,
pathseg=UIO_USERSPACE) at /usr/src/sys/kern/vfs_syscalls.c:3211
#10 0xc0510f55 in rename (td=0x0, uap=0x0) at
/usr/src/sys/kern/vfs_syscalls.c:3167
#11 0xc060fe1f in syscall (frame=
      {tf_fs = 135069755, tf_es = 135069755, tf_ds = -1078001605, tf_edi =
135127484, tf_esi = 135127472, tf_ebp = -1077944856, tf_isp = -558523036,
tf_ebx = 135097024, tf_edx = -1077944240, tf_ecx = 135097024, tf_eax = 128,
tf_trapno = 12, tf_err = 2, tf_eip = 674283299, tf_cs = 51, tf_eflags = 582,
tf_esp = -1077944900, tf_ss = 59}) at /usr/src/sys/i386/i386/trap.c:976
#12 0xc05fc3df in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:200
#13 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)

the thing is that I don't really know what could have caused that.

-- 
Mathieu Arnold


More information about the freebsd-stable mailing list