Date: Tue, 02 Jun 1998 15:44:54 -0700 From: David Greenman <dg@root.com> To: Scott Drassinower <scottd@cloud9.net> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems Message-ID: <199806022244.PAA18069@implode.root.com> In-Reply-To: Your message of "Tue, 02 Jun 1998 10:12:30 EDT." <Pine.BSF.3.96.980602093249.29838D-100000@earl-grey.cloud9.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>netstat -i on the client has no interface errors, netstat -i on the server >has one output error but no input errors. I'm not too surprised by this; the one case where I saw the lossage problem with the Cisco didn't show any errors on either side, yet there was 20% packet loss. I'm sure if I had been using NFS in that case that things would have sucked badly. >I might be able to get a hold of another 100 megabit switch, perhaps an >Intel, and we can see if the problem goes away or if it's the same. I'm >wondering if there are other people running 100 megabit that might be able >to duplicate this problem. I use Intel Pro/100B and 100+ cards in all of my machines here on a fast ether switch in full duplex with NFS. I've never had any problems. We also do the same with freefall/hub/etc. While we've had problems with NFS there when one of the machines goes down, I don't recall seeing any problems like you're having with selective processes wedging. -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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806022244.PAA18069>