From owner-freebsd-current Tue Oct 1 18:14:39 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 E2C4237B401 for ; Tue, 1 Oct 2002 18:14:38 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BEFE43E6E for ; Tue, 1 Oct 2002 18:14:31 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g921E9vU014644; Tue, 1 Oct 2002 18:14:13 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200210020114.g921E9vU014644@gw.catspoiler.org> Date: Tue, 1 Oct 2002 18:14:09 -0700 (PDT) From: Don Lewis Subject: Re: system lockup: nfs server not responding 10 > 9 (tx driver bug?) To: sam@errno.com Cc: current@FreeBSD.ORG In-Reply-To: <138d01c269ae$766ee400$52557f42@errno.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=Windows-1252 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 On 1 Oct, Sam Leffler wrote: > I have repeated problems where a machine running -current locks up while > running make over an NFS mounted filesystem. The NFS server is an up to > date -stable machine. When the lockup occurs I get a message: > > nfs server : not responding 10 > 9 > > The filesystem is mounted r/w with no options. nfsiod's 0, 1, and 2 are in > DL, 3 is in IL state. nfsiod 0 is sleeping on sbwait. > > The -current machine is up to date. 100 Mb/s Ethernet. tx driver. When > the lockup occurs I can still login to the console but the network appears > dead (no packets appear to pass). > > Looks like maybe a tx driver bug. Anyone seen this with other NIC's? I haven't had any problems doing read-only accesses of my nfs mounted CVS respository via an fxp NIC. There are definitely some issues in the vnode locking in the NFS code that get caught if by turning on vnode lock checking stuff. I don't think this would be causing the problem you're seeing, though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message