From owner-freebsd-current@FreeBSD.ORG Wed Sep 8 01:15:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BAAD16A4CE for ; Wed, 8 Sep 2004 01:15:48 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47B9543D45 for ; Wed, 8 Sep 2004 01:15:48 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([141.153.207.21]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040908011547.ECDT24594.out001.verizon.net@[10.0.3.231]> for ; Tue, 7 Sep 2004 20:15:47 -0500 From: "Alexandre \"Sunny\" Kovalenko" To: freebsd-current@freebsd.org In-Reply-To: <20040907161851.GA67411@parodius.com> References: <20040907112121.GA94401@cell.sick.ru> <20040907151957.GE95626@cell.sick.ru> <1094571416.67273.8.camel@rushlight.kf8nh.com> <20040907161851.GA67411@parodius.com> Content-Type: text/plain Message-Id: <1094606114.673.9.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 07 Sep 2004 21:15:15 -0400 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [141.153.207.21] at Tue, 7 Sep 2004 20:15:47 -0500 Subject: Re: BETA3 showstoppers (read: critical bugs) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2004 01:15:48 -0000 On Tue, 2004-09-07 at 12:18, Jeremy Chadwick wrote: > I can confirm Brandon's comments (re: 802.3 speed/duplex negotiation not > working properly with Cisco equipment). At Best, we had to force duplex > and speed on both our Catalysts and our BSD boxes, otherwise, mysterious > problems would occur (slow transfer rates in one direction, input or > output errors, etc.). I'm sure Matt Dillon can attest to this as well. > > I highly doubt it's specific to the xl driver, or even 3Com cards, since > 4-5 months ago I had such issues connecting a Catalyst to an HP ProCurve > switch -- again, had to force the speed and duplex on both ends. I think > this is a pretty "historic" problem with Cisco equipment. Look around > the Web and you'll see what I mean. > > The procedure, if I remember right: > > Cat> set port x/y speed 100 > Cat> set port x/y duplex full > Cat> set port disable x/y > > BSD> ifconfig xl0 ... media 100baseTX mediaopt full-duplex > BSD> [see note] > > Cat> set port enable x/y > > NOTE: Occasionally I'd also see this procedure fail until the BSD box was > actually *rebooted*. This problem always eluded me, but may have > changed severely since the days of 2.2.8 ( :) ). FWIW: I have autonegotiation problems between Cisco switches and way too many pieces of equipment to list here (including, but not limited to: several models of IBM RS/6000, couple of Sun boxes, fxp & bge under Windows/Linux/FreeBSD, etc.). Forcing speed to 100-FDX solves the problem for good. Usual symptoms -- under heavy load transfer speeds slows to crawl and connection is being dropped eventually. Only common denominator is Cisco switch. HTH. --- Alexandre "Sunny" Kovalenko.