From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 16:06:51 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78B011065675 for ; Tue, 23 Sep 2008 16:06:51 +0000 (UTC) (envelope-from freebsd-hackers@wheelhouse.org) Received: from mail.nearlyfreespeech.net (x1.phxe.nearlyfreespeech.net [208.94.116.235]) by mx1.freebsd.org (Postfix) with ESMTP id 53CF58FC1C for ; Tue, 23 Sep 2008 16:06:51 +0000 (UTC) (envelope-from freebsd-hackers@wheelhouse.org) Received: from [10.0.1.201] (78.193.33.65.cfl.res.rr.com [65.33.193.78]) by mail.nearlyfreespeech.net (Postfix) with ESMTPSA id 4DFD1EBC77 for ; Tue, 23 Sep 2008 08:51:29 -0700 (MST) Message-Id: From: Jeff Wheelhouse To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 23 Sep 2008 11:51:28 -0400 X-Mailer: Apple Mail (2.929.2) Subject: panic: lockmgr on FreeBSD 7.0-RELEASE-p4 amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2008 16:06:51 -0000 Got the following panic overnight: panic: lockmgr: thread 0xffffff0053cda680, not exclusive lock holder 0xffffff002d7da680 unlocking cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x17a _lockmgr() at _lockmgr+0x872 VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46 null_unlock() at null_unlock+0xff VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46 nullfs_mount() at nullfs_mount+0x244 vfs_donmount() at vfs_donmount+0xe4d nmount() at nmount+0xa5 syscall() at syscall+0x254 Xfast_syscall() at Xfast_syscall+0xab --- syscall (378, FreeBSD ELF64, nmount), rip = 0x206845ac, rsp = 0x7fffffffdfb8, rbp = 0x7fffffffdfc0 --- I've done some searches and "not exclusive lock holder" has been seen before, but I didn't find any previous reports related to nullfs with a stack trace at all like this on FreeBSD 7. This machine is diskless and thus cannot store a kernel dump. Ideas/ suggestions for fixes, causes or debugging steps? The kernel is amd64, with config shown below. Thanks, Jeff include GENERIC device carp device pf device pflog device pfsync options SW_WATCHDOG options DEVICE_POLLING options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_PRIQ options ALTQ_NOPCC options KDB options KDB_UNATTENDED options KDB_TRACE options DDB options BREAK_TO_DEBUGGER