From owner-freebsd-current@FreeBSD.ORG Wed Sep 28 18:59:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49C5816A41F for ; Wed, 28 Sep 2005 18:59:52 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D823A43D53 for ; Wed, 28 Sep 2005 18:59:51 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Wed, 28 Sep 2005 23:00:27 +0400 From: Artemiev Igor To: freebsd-current@freebsd.org Message-ID: <20050928190027.GA1028@bmc.brk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: current-i386: thread 0xc07686a0 unlocking unheld lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2005 18:59:52 -0000 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