From owner-freebsd-stable@FreeBSD.ORG Mon Nov 6 21:51:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 393FD16A494 for ; Mon, 6 Nov 2006 21:51:42 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [63.240.77.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6FA343D6A for ; Mon, 6 Nov 2006 21:51:40 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc11) with ESMTP id <2006110621513501100ch8pse>; Mon, 6 Nov 2006 21:51:39 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 22BE81FA01A; Mon, 6 Nov 2006 13:51:35 -0800 (PST) Date: Mon, 6 Nov 2006 13:51:35 -0800 From: Jeremy Chadwick To: Matthew Seaman Message-ID: <20061106215135.GA6320@icarus.home.lan> Mail-Followup-To: Matthew Seaman , sthaug@nethelp.no, valqk@lozenetz.org, freebsd-stable@freebsd.org, tom@samplonius.org References: <454BC211.3090104@lozenetz.org> <454F010D.4090807@lozenetz.org> <20061106114537.GA99879@icarus.home.lan> <20061106.222443.74711080.sthaug@nethelp.no> <454FAB16.1040608@infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <454FAB16.1040608@infracaninophile.co.uk> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org, valqk@lozenetz.org, tom@samplonius.org, sthaug@nethelp.no Subject: Re: netstat -ni - A lot of collisions... 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: Mon, 06 Nov 2006 21:51:42 -0000 On Mon, Nov 06, 2006 at 09:37:26PM +0000, Matthew Seaman wrote: > We've had a series of Broadcomm bge(4) network interfaces that would > arbitrarily stop working if hardwired to 100-full, but that are doing > just fine when allowed to autoneg. Switches are mostly HP Procurve if > that makes any difference. Interesting. I've got a ProCurve 2524 in our co-lo with tons of FreeBSD boxes hooked to it, all of which behave correctly via auto-neg. The FreeBSD boxes use a slew of NICs; em, fxp, and xl. The uplink port on our 2524 to our ISP, however, has to be set to 100/full on both ends (theirs and ours; theirs = Cisco, ours = HP) or else we end up with framing errors and other nonsense. For sake of comparison, I have sitting in my workroom a bge-based box hooked up to a ProCurve 2626 which behaves properly via auto-neg on both the 100mbit and the gigabit ports (I've tried both). I have not tried hard-setting them, since auto-neg seems to work. However, the instant I hook that box up to my Hawking non-managed gigabit switch (which is a switch where auto-neg has worked with every NIC I've tried until now), the switch and NIC auto-neg correctly to 1gb/full... except packets appear busted in some way: packets make it to the switch (one can see the LEDs blinking), yet the IP stack doesn't see anything in return. ARP also does not show anything. The fact that auto-neg is working, and that the switch indicates correct speed and duplex, makes me think this is some weird bge driver problem. Wiring is all CAT6, and obviously works fine with another switch. If I set `media 100baseTX mediaopt full-duplex` and reboot, everything works (at 100mbit of course) with that box. I'd love to give a kernel developer access to that box via serial console so they could debug what the heck is going on with auto-neg in that particular case. :-) -- | 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 |