From owner-freebsd-current Tue Mar 18 7:15: 7 2003 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 7FC8F37B401 for ; Tue, 18 Mar 2003 07:15:06 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FB7343FA3 for ; Tue, 18 Mar 2003 07:15:05 -0800 (PST) (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.12.8/8.12.8) with ESMTP id h2IFF2Rv000062 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Mar 2003 10:15:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h2IFEvV00417; Tue, 18 Mar 2003 10:14:57 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15991.14321.592523.62688@grasshopper.cs.duke.edu> Date: Tue, 18 Mar 2003 10:14:57 -0500 (EST) To: Jeff Roberson Cc: freebsd-current@FreeBSD.ORG Subject: Re: nfs panic: lockmgr: locking against myself In-Reply-To: <20030317195946.W66343-100000@mail.chesapeake.net> References: <15990.28152.594563.16107@grasshopper.cs.duke.edu> <20030317195946.W66343-100000@mail.chesapeake.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 Jeff Roberson writes: > On Mon, 17 Mar 2003, Andrew Gallatin wrote: > > > > > I'm seeing the following panic under heavy NFS client usage on an SMP > > w/kernel sources from Weds. evening. Has this been fixed? > > > > Thanks, > > > > Drew > > I believe that is fixed in nfs_vnops.c 1.200. > Yep, it seems to be fixed now. Thanks! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message