From owner-freebsd-current Sun Oct 20 3:27: 9 2002 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 CE64137B401 for ; Sun, 20 Oct 2002 03:26:56 -0700 (PDT) Received: from blarf.homeip.net (adsl-209-204-188-56.sonic.net [209.204.188.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id C168A43E91 for ; Sun, 20 Oct 2002 03:26:55 -0700 (PDT) (envelope-from sonicmail@blarf.homeip.net) Received: by blarf.homeip.net (Postfix, from userid 1006) id 53C651831; Sun, 20 Oct 2002 03:26:54 -0700 (PDT) Date: Sun, 20 Oct 2002 03:26:54 -0700 From: Alex Zepeda To: current@freebsd.org Subject: kernel: lock order reversal Message-ID: <20021020102654.GA47626@blarf.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I see this on a fairly regular basis (at least once per 24 hour period): lock order reversal 1st 0xc0490ca0 spechash (spechash) @ ../../../kern/vfs_subr.c:2748 2nd 0xc1ed2818 vnode interlock (vnode interlock) @ ../../../kern/vfs_subr.c:2751 Dunno if it's any help, but it happened at 03:08:50, so right towards the midle of the daily scripts (takes about 20mins here), fairly heavy disk access. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message