From owner-freebsd-hackers Mon Aug 11 17:02:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09184 for hackers-outgoing; Mon, 11 Aug 1997 17:02:32 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA09174 for ; Mon, 11 Aug 1997 17:02:29 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA19545; Mon, 11 Aug 1997 17:04:44 -0700 (PDT) Message-Id: <199708120004.RAA19545@implode.root.com> To: Tom Samplonius cc: hackers@FreeBSD.ORG Subject: Re: fxp driver full duplex packet loss problem In-reply-to: Your message of "Mon, 11 Aug 1997 12:16:33 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 11 Aug 1997 17:04:43 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have a Intel Etherexpress Pro100/B conneted into a 10BT port on a >lightly loaded Catlyst 1900 etherswitch. The system is running 2.2-stable >(last week), and traffic ranges from about 50 to 150KB/s output (as >measured with netstat -I fxp0 -w 1) > > When I use "link0 link2" to enable full-duplex operation, I start seeing >about 1 to 4% packet loss (measured with ping to and from the server). >When I disable full-duplex, the packet loss disappears. > > Is it safe to change the full-duplex vs. half-duplex on-the-fly? Should >I power-cycle/reboot between changes? > > Anyone else running this card in this kind of configuration? At least some Cisco fast ethernet interfaces (those on the 7000/7500 series routers, for instance), don't support auto-negotiation. So when you force full duplex on your end, the Cisco is still in half duplex. The behavior you're describing is indicative of this. To fix this, you'll need to set full duplex in the Cisco as well. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project