From owner-freebsd-current@FreeBSD.ORG Tue Oct 4 19:57:51 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 0C56816A41F for ; Tue, 4 Oct 2005 19:57:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22B443D45 for ; Tue, 4 Oct 2005 19:57:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [70.30.70.180]) by elvis.mu.org (Postfix) with ESMTP id 9BF7F1A3C1E; Tue, 4 Oct 2005 12:57:43 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8B9D75130C; Tue, 4 Oct 2005 15:57:42 -0400 (EDT) Date: Tue, 4 Oct 2005 15:57:42 -0400 From: Kris Kennaway To: Andrew Gallatin Message-ID: <20051004195742.GA56798@xor.obsecurity.org> References: <17218.49812.271334.154595@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <17218.49812.271334.154595@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: 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 19:57:51 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 04, 2005 at 01:57:40PM -0400, Andrew Gallatin wrote: >=20 > I'm getting tons of these warnings on a new AMD64x2 box when doing > heavy disk activity (buildworld or portsnap): >=20 > 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 =3D 0x8006e2f4c, rsp =3D 0x7fff= ffffe638, rbp =3D 0x4 --- >=20 > 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. >=20 > Kris reported the same message, but with a different stack here: > http://lists.freebsd.org/pipermail/freebsd-current/2005-September/055142.= html What filesystems are you using? Any non-standard kernel options? I've not seen any more of these on nullfs, nfs or ufs in my environment (mine were nullfs-related). Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDQt62Wry0BWjoQKURAjssAJ0R38zwvBkZtv+cQGKaTO1I8Aty6wCgrKFN Hnwufv6pPhFFCXD9C/WEfuI= =OZGI -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU--