From owner-freebsd-net@FreeBSD.ORG Tue Aug 10 21:41:56 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A31716A4CE for ; Tue, 10 Aug 2004 21:41:56 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 323B143D49 for ; Tue, 10 Aug 2004 21:41:55 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i7ALfs2G006283; Tue, 10 Aug 2004 14:41:54 -0700 (PDT) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i7ALfafs028326; Tue, 10 Aug 2004 14:41:39 -0700 (PDT) In-Reply-To: <20040810173211.V776@ganymede.hub.org> References: <20040810173211.V776@ganymede.hub.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0D70424D-EB16-11D8-BAD8-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 10 Aug 2004 17:41:35 -0400 To: "Marc G. Fournier" X-Mailer: Apple Mail (2.619) cc: freebsd-net@freebsd.org Subject: Re: em driver worse then fxp driver ... why? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 21:41:56 -0000 [ ...crossposting between stable and freebsd-net trimmed... ] On Aug 10, 2004, at 4:37 PM, Marc G. Fournier wrote: > I've tried in bth half and full duplex mode .. full duplex, Ierrs > climbs, half-duplex, Collisions climb ... You should expect to see some collisions (1% or so) when working in half-duplex mode: that's the nature of the beast. Is your Linksys switch managed or unmanaged? If you can set both it and the em to manually configured 100/FD, that would be worth trying. I'd also try swapping a cable plugged into a working fxp box with the machine using the em, and see whether the problems follow, or whether the fxp system starts having issues. A bad cable or a flaky port on the switch could also be causing your problems, but ethernet autonegotiation failing seems to be more likely given the description. -- -Chuck