current-i386: thread 0xc07686a0 unlocking unheld lock

From: Artemiev Igor <ai_at_bmc.brk.ru>
Date: Wed, 28 Sep 2005 23:00:27 +0400
I received this message during the reboot after the update last night:

lockmgr: thread 0xc07686a0 unlocking unheld lock
KDB: stack backtrace:
kdb_backtrace(c070a80b,c07686a0,c07766ac,c0c20cec,c053ebd7) at kdb_backtrace+0x2
e
lockmgr(c0776688,6,c07766ac,c07686a0,c0c20d28) at lockmgr+0x5d0
smb_co_unlock(c0776680,0,c07686a0,c07686a0,c0c20d48) at smb_co_unlock+0x2c
smb_sm_init(c0c20d48,c0541ab4,c19802ac,c0716652,c1980280) at smb_sm_init+0x4a
nsmb_dev_load(c1980280,0,0,0,0) at nsmb_dev_load+0x25
module_register_init(c074c864,c1e000,c1ec00,c1e000,0) at module_register_init+0x
81
mi_startup() at mi_startup+0x99
begin() at begin+0x2c
netsmb_dev: loaded

Looks like the curthread was changed, but lk_lockholder remained the same, and because of that, lock is not released now by lockmgr(). Why?
I use SCHED_ULE with PREEMPTION+ADAPTIVE_GIANT+MUTEX_WAKE_ALL. NETSMB compiled into kernel.

-- 
iprefetch ai
Received on Wed Sep 28 2005 - 16:59:52 UTC

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