From owner-freebsd-stable Fri Apr 5 16:30:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mighty.grot.org (mighty.grot.org [204.182.56.120]) by hub.freebsd.org (Postfix) with ESMTP id CD7BE37B417 for ; Fri, 5 Apr 2002 16:30:42 -0800 (PST) Received: by mighty.grot.org (Postfix, from userid 515) id 84F3C5E89; Fri, 5 Apr 2002 16:30:37 -0800 (PST) Date: Fri, 5 Apr 2002 16:30:37 -0800 From: Aditya To: freebsd-stable@freebsd.org Subject: NFS hang with fxp and Network Appliance fileserver Message-ID: <20020406003037.GA72332@mighty.grot.org> Reply-To: Aditya Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://www.grot.org/pubkey.asc X-PGP-Key-ID: 0x6405D8D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have 2 different motherboards, one with 2 fxp's on board the other with a fxp in a slot mounting a Network Appliance (NetApp) fileserver over a directly-connected, otherwise quiet 100Mbit, full-duplex switched ethernet. *All* ethernet interfaces and switch ports are hard-wired to 100baseTX full-duplex. The clients are both running 4.5-STABLE cvsupped on Feb 27th. The NetApp is running OnTAP 6.1.2R1 and works fine with a similar client with a de (Tulip) SMC card over the same network (my test is building world). In order to get the fxp connected clients to not hang after just a few NFS requests, I have to mount it with the -r=1024 option as recommended in the handbook under the "Problems integrating with other systems" in the NFS section. That text refers to "Certain Ethernet adapters for ISA PC systems" but seems to be applicable for more modern, PCI cards too... If this is the "correct" method to deal with the fxp cards, then should the text be amended or should the fxp driver be "fixed"? Thanks, Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message