From owner-freebsd-current@FreeBSD.ORG Fri Aug 27 02:04:46 2004 Return-Path: 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 D0BBD16A4CE; Fri, 27 Aug 2004 02:04:46 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C20F843D3F; Fri, 27 Aug 2004 02:04:46 +0000 (GMT) (envelope-from kan@FreeBSD.org) Received: from freefall.freebsd.org (kan@localhost [127.0.0.1]) i7R24kw3025223; Fri, 27 Aug 2004 02:04:46 GMT (envelope-from kan@freefall.freebsd.org) Received: (from kan@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7R24k7p025222; Fri, 27 Aug 2004 02:04:46 GMT (envelope-from kan) Date: Fri, 27 Aug 2004 02:04:46 +0000 From: Alexander Kabaev To: Brian Fundakowski Feldman Message-ID: <20040827020446.GB24979@freefall.freebsd.org> References: <20040826062416.GA36168@peter.osted.lan> <20040826201748.GR77326@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040826201748.GR77326@green.homeunix.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: panic: vrele: negative ref cnt @ kern/vfs_subr.c:2141 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 27 Aug 2004 02:04:46 -0000 On Thu, Aug 26, 2004 at 04:17:48PM -0400, Brian Fundakowski Feldman wrote: > On Thu, Aug 26, 2004 at 08:24:16AM +0200, Peter Holm wrote: > > Current from Aug 25 05:04 (Aug 25 03:04 UTC). > > More info at http://www.holm.cc/stress/log/cons68.html > > I wonder if the upcoming lockmgr(9) changes will affect this. > > -- > Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ > <> green@FreeBSD.org \ The Power to Serve! \ > Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ Highly unlikely. There were numerous reports about this panic already well before any of the recent lockmgr changes were committed. Besides, Peter was testing the latest lockmgr fix in his environment and I assume he got this panic on a patched system. -- Alexander Kabaev