unlocking unheld lock with Jun 3 -CURRENT

[Matthew D. Fuller]

I just updated one of my -CURRENT machines, and I'm getting a lockmgr
message during bootup.

----
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
lockmgr: thread 0xc07972f8 unlocking unheld lock
KDB: stack backtrace:
lockmgr(c07a6088,6,c07a60ac,c07972f8,c0c20d3c) at lockmgr+0x452
smb_co_unlock(c07a6080,0,c07972f8,c0c20d48,c061a8dd) at
smb_co_unlock+0x1d
smb_sm_init(c2fe5400,c0c20d74,c0567d6b,c2fe5400,0) at smb_sm_init+0x30
nsmb_dev_load(c2fe5400,0,0,c0797de0,c071adf3,78) at nsmb_dev_load+0x18
module_register_init(c0778830,c1ec00,c1e000,0,c0448f05) at
module_register_init+
0x50
mi_startup() at mi_startup+0x86
begin() at begin+0x2c
netsmb_dev: loaded
sequencer 0 created scp 0xc2feae00
acpi0: <PTLTD   RSDT> on motherboard
----

I've not tried using the smbfs stuff (which that seems from) yet, but
nothing else seems broken.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.