From owner-freebsd-current@FreeBSD.ORG Tue Oct 4 17:57:47 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 284FF16A41F for ; Tue, 4 Oct 2005 17:57:47 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC81A43D48 for ; Tue, 4 Oct 2005 17:57:46 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.4/8.13.4) with ESMTP id j94Hvjbw019262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 4 Oct 2005 13:57:45 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id j94HveaW084841; Tue, 4 Oct 2005 13:57:40 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17218.49812.271334.154595@grasshopper.cs.duke.edu> Date: Tue, 4 Oct 2005 13:57:40 -0400 (EDT) To: freebsd-current@freebsd.org X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: lockmgr: thread <..> 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: Tue, 04 Oct 2005 17:57:47 -0000 I'm getting tons of these warnings on a new AMD64x2 box when doing heavy disk activity (buildworld or portsnap): lockmgr: thread 0xffffff00162a1be0 unlocking unheld lock KDB: stack backtrace: lockmgr() at lockmgr+0x6ee VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x49 vput() at vput+0x81 lookup() at lookup+0xae2 namei() at namei+0x34d vn_open_cred() at vn_open_cred+0x208 kern_open() at kern_open+0xfc open() at open+0x25 syscall() at syscall+0x642 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (5, FreeBSD ELF64, open), rip = 0x8006e2f4c, rsp = 0x7fffffffe638, rbp = 0x4 --- This is with -current as of ~9am EDT today. I've seen 19 in the course of a j4 buildworld and a portsnap fetch and extract. Kris reported the same message, but with a different stack here: http://lists.freebsd.org/pipermail/freebsd-current/2005-September/055142.html Drew