PANIC not exclusive lock holder 5.2R

Got a Panic this morning with 5.2R after 13days of uptime.  Is this a
known issue?  I could not find an open bug report or anything in the
archives.   If not known I would be happy to help debug if needed or
provide additional info.  I am set to stop at debugger on panic and
core file is saved.
Ken

Details of error:
Jan 27 08:32:58 riker savecore: reboot after panic: lockmgr: thread
0xc88e6dc0,
not exclusive lock holder 0xc820ec80 unlocking
Jan 27 08:32:58 riker savecore: unable to open bounds file, using 0
Jan 27 08:32:58 riker savecore: writing core to vmcore.0
Version:
FreeBSD riker.icarz.com 5.2-RELEASE FreeBSD 5.2-RELEASE #6: Tue Jan 13
13:41:17 EST 2004
sysadm_at_riker.icarz.com:/usr/obj/usr/src/sys/ICARZ  i386

(kgdb) bt
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1  0xc0622b06 in boot (howto=256) at
/usr/src/sys/kern/kern_shutdown.c:372
#2  0xc0622f4f in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc061501e in lockmgr (lkp=0xc91125c0, flags=6,
interlkp=0x1000040,
    td=0xc88e6dc0) at /usr/src/sys/kern/kern_lock.c:414
#4  0xc0679fef in vop_stdunlock (ap=0x0) at
/usr/src/sys/kern/vfs_default.c:299
#5  0xc0679e58 in vop_defaultop (ap=0x0) at
/usr/src/sys/kern/vfs_default.c:161
#6  0xc078a2f8 in ufs_vnoperate (ap=0x0)
    at /usr/src/sys/ufs/ufs/ufs_vnops.c:2793
#7  0xc0781e19 in ufs_inactive (ap=0x0) at vnode_if.h:1044
#8  0xc078a2f8 in ufs_vnoperate (ap=0x0)
    at /usr/src/sys/ufs/ufs/ufs_vnops.c:2793
#9  0xc06848b8 in vrele (vp=0xc9112514) at vnode_if.h:953
#10 0xc07862f4 in ufs_close (ap=0x0) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:319
#11 0xc078a2f8 in ufs_vnoperate (ap=0x0)
    at /usr/src/sys/ufs/ufs/ufs_vnops.c:2793
#12 0xc0690ac6 in vn_close (vp=0xc88e6dc0, flags=0, file_cred=0x0,
td=0x0)
    at vnode_if.h:262
#13 0xc0691a30 in vn_closefile (fp=0x0, td=0x0)
    at /usr/src/sys/kern/vfs_vnops.c:908
#14 0xc0601ab9 in fdrop_locked (fp=0xc9112514, td=0x0)
    at /usr/src/sys/sys/file.h:292
#15 0xc06005cf in fdrop (fp=0xc9112514, td=0x0)
---Type <return> to continue, or q <return> to quit---
    at /usr/src/sys/kern/kern_descrip.c:1829
#16 0xc0600552 in closef (fp=0xc8723ee0, td=0xc88e6dc0)
    at /usr/src/sys/kern/kern_descrip.c:1815
#17 0xc05ff996 in fdfree (td=0xc88e6dc0)
    at /usr/src/sys/kern/kern_descrip.c:1519
#18 0xc0607a99 in exit1 (td=0xc88e6dc0, rv=0)
    at /usr/src/sys/kern/kern_exit.c:247
#19 0xc0607457 in sys_exit () at /usr/src/sys/kern/kern_exit.c:102
#20 0xc07e7420 in syscall (frame=
      {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = -1,
tf_ebp = -1077943000, tf_isp = -428384908, tf_ebx = 1754579232, tf_edx
= 10, tf_ecx = 1754578896, tf_eax = 1, tf_trapno = 12, tf_err = 2,
tf_eip = 1754066587, tf_cs = 31, tf_eflags = 642, tf_esp
= -1077943028, tf_ss = 47})
    at /usr/src/sys/i386/i386/trap.c:1010
#21 0xc07d281d in Xint0x80_syscall () at {standard input}:136
---Can't read userspace from dump, or kernel process---


-----------------------------------------------------
Ken Menzel  ICQ# 9325188
www.icarz.com  kenm_at_icarz.com