Re: lockmgr panic on shutdown

More info.

I think this is actually related to kan's reversion of
src/sys/kern/vfs_default.c.  I'm trying rev 1.88 of that file.

In the meantime, here is the panic message and backtrace. I have a
crashdump if desired.

panic: lockmgr: thread 0xc493be40, not exclusive lock holder 0xc071f320 unlocking

#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1  0xc0510884 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2  0xc0510be7 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc05043ea in lockmgr (lkp=0xc49af428, flags=6, interlkp=0x1000040,
    td=0xc493be40) at /usr/src/sys/kern/kern_lock.c:414
#4  0xc055e91f in vop_stdunlock (ap=0x0) at /usr/src/sys/kern/vfs_default.c:299
#5  0xc055e768 in vop_defaultop (ap=0x0) at /usr/src/sys/kern/vfs_default.c:161
#6  0xc061ed88 in ufs_vnoperate (ap=0x0)
    at /usr/src/sys/ufs/ufs/ufs_vnops.c:2793
#7  0xc06173d0 in ufs_inactive (ap=0x0) at vnode_if.h:1044
#8  0xc061ed88 in ufs_vnoperate (ap=0x0)
    at /usr/src/sys/ufs/ufs/ufs_vnops.c:2793
#9  0xc05686d7 in vput (vp=0xc49af36c) at vnode_if.h:953
#10 0xc0610245 in ffs_sync (mp=0xc47b2800, waitfor=2, cred=0xc1d07e80,
    td=0xc071f320) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1169
#11 0xc056ade4 in sync (td=0xc071f320, uap=0x0)
    at /usr/src/sys/kern/vfs_syscalls.c:142
#12 0xc05103e0 in boot (howto=8) at /usr/src/sys/kern/kern_shutdown.c:281
#13 0xc0510046 in reboot (td=0x0, uap=0x0)
    at /usr/src/sys/kern/kern_shutdown.c:178
#14 0xc066cf32 in syscall (frame=
      {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 0, tf_ebp = -1077937104, tf_isp = -574005900, tf_ebx = 2, tf_edx = -1, tf_ecx = 3, tf_eax = 55, tf_trapno = 12, tf_err = 2, tf_eip = 134516011, tf_cs = 31, tf_eflags = 582, tf_esp = -1077937172, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1012
#15 0xc065d91d in Xint0x80_syscall () at {standard input}:144


On Sat, 1 Nov 2003, Doug White wrote:

> I can confirm the lockmgr panic on shutdown reported by someone else
> earlier (whose message I mistakenly deleted).
>
> It looks like swapper is trying to undo a lock from pagedaemon and runs
> into trouble. This is probably related to the Giant pushdown of
> vm_pageout() that alc did last week.
>
> I'm building with INVARIANTS to see if that will catch more info.  Will
> report back soon.
>
>

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite_at_gumbysoft.com          |  www.FreeBSD.org