From owner-freebsd-hardware Mon Jun 1 21:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06250 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 21:32:56 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06230 for ; Mon, 1 Jun 1998 21:32:49 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA12291; Mon, 1 Jun 1998 21:32:13 -0700 (PDT) Message-Id: <199806020432.VAA12291@implode.root.com> To: Scott Drassinower cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-reply-to: Your message of "Mon, 01 Jun 1998 10:07:09 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Jun 1998 21:32:13 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >So the problem that I'm having with NFS will likely occur with a 3Com or >SMC card as well? There is no workaround at all for this, just deal with >messed up nfs or run at 10 megabits? I was only suggesting that our NFS has problems in some corner cases. Usually this only shows up when there are multiple clients writing to the same file, and the usual result is file corruption, not a client/server wedge. Our NFS also doesn't recover properly from certain kinds of failures. All of these issues are being looked at in -current and there have been a few fixes that have trickled back to -stable...not that I think those will fix your problem, however. I think your troubles are at the link level and are symptoms of packet loss. Try setting both sides to forced 100/half. I've had some compatiblity problems with Cisco router-switches when connected to other vendor switches in 100/full. For some reason switching to half duplex causes the problems to go away (and it's not actually a duplex problem as that was verified to be correct on both ends...weird). I haven't seen the problems you are having with NFS and the Cisco/Intel combination. It sounds like there is packet loss in some cases which is causing NFS clients to wedge. Are you sure that your cable is up to spec? Are there any interface errors on either side? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message