From owner-freebsd-stable@FreeBSD.ORG Wed Jan 24 15:01:53 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3260C16A402 for ; Wed, 24 Jan 2007 15:01:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.192.83]) by mx1.freebsd.org (Postfix) with ESMTP id 1DC7513C4D0 for ; Wed, 24 Jan 2007 15:01:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-71-198-0-135.hsd1.ca.comcast.net[71.198.0.135]) by comcast.net (rwcrmhc13) with ESMTP id <20070124150152m1300pgr6ke>; Wed, 24 Jan 2007 15:01:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 36C8E1FA037; Wed, 24 Jan 2007 07:01:43 -0800 (PST) Date: Wed, 24 Jan 2007 07:01:43 -0800 From: Jeremy Chadwick To: Robin Gruyters Message-ID: <20070124150143.GA8460@icarus.home.lan> Mail-Followup-To: Robin Gruyters , freebsd-stable@FreeBSD.org References: <20070124105741.cj2htvoxcs4gg8wk@server.yirdis.net> <20070124141737.GA7772@icarus.home.lan> <20070124152537.gk06yc8d3k8gwgo0@server.yirdis.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070124152537.gk06yc8d3k8gwgo0@server.yirdis.net> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@FreeBSD.org Subject: Re: bge Ierr rate increase from 5.3R -> 6.1R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 15:01:53 -0000 On Wed, Jan 24, 2007 at 03:25:37PM +0100, Robin Gruyters wrote: > Should this not be visible on the switch as well?!? > > Here some output from the interface on the server and from the switch > (Cisco) > > [development interface] > bge0: flags=8843 mtu 1500 > options=1b > ether 00:12:79:94:ed:12 > media: Ethernet autoselect (100baseTX ) > status: active > [/development interface] > > [switch] > FastEthernet0/3 is up, line protocol is up (connected) > Hardware is Fast Ethernet, address is 000e.84d0.de03 (bia 000e.84d0.de03) > Description: development > MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation ARPA, loopback not set > Keepalive set (10 sec) > Full-duplex, 100Mb/s > input flow-control is off, output flow-control is off > ARP type: ARPA, ARP Timeout 04:00:00 > Last input never, output 00:00:02, output hang never > Last clearing of "show interface" counters never > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > Queueing strategy: fifo > Output queue: 0/40 (size/max) > 5 minute input rate 179000 bits/sec, 28 packets/sec > 5 minute output rate 56000 bits/sec, 24 packets/sec > 22823978 packets input, 4067576147 bytes, 0 no buffer > Received 13138 broadcasts (0 multicast) > 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 0 watchdog, 12929 multicast, 0 pause input > 0 input packets with dribble condition detected > 15673035 packets output, 3975127029 bytes, 0 underruns > 0 output errors, 0 collisions, 1 interface resets > 0 babbles, 0 late collision, 0 deferred > 0 lost carrier, 0 no carrier, 0 PAUSE output > 0 output buffer failures, 0 output buffers swapped out > [/switch] You've got a Cisco involved, so I doubt it. :-) I've seen many times in the past where one end of the link shows errors while the other end (in my experiences, Cisco Catalysts) shows none. When dealing with Cisco<->othervendor, I've never seen auto-neg work properly. One has to always hard set the speed and duplex on both sides for it to work. For example: I lease space in two co-location facilities, from different providers. Both providers use Cisco switches (different models), while we use HP ProCurves. In both facilities, we saw input errors on our ProCurve, while the providers saw absolutely no errors. Both sides were set to auto. The instant I had the providers set 100/full on their Ciscos and I set 100/FD on our ProCurves, the error counts completely disappeared. Set your Cisco configuration to use 100/full, and edit the ifconfig_bge0 line in rc.conf on your FreeBSD box to have "media 100baseTX mediaopt full-duplex", then reboot the FreeBSD box. If the problem continues, there may be faulty cabling, but usually errors on one direction are a sign of duplex mismatch. If after replacing the cabling the issue continues, then there's a chance the bge(4) driver may be obtaining statistics wrong for the particular chip revision being used (this is hearsay on my part; I'm just guessing...) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |