From owner-freebsd-current@FreeBSD.ORG Tue Feb 19 08:23:02 2013 Return-Path: Delivered-To: current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id C97233C7; Tue, 19 Feb 2013 08:23:02 +0000 (UTC) Date: Tue, 19 Feb 2013 08:23:02 +0000 From: Alexey Dokuchaev To: current@freebsd.org Subject: ale(4) cannot negotiate as GigE Message-ID: <20130219082302.GA86501@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 19 Feb 2013 08:23:02 -0000 Hi there, I've recently put back online one of my home servers, updated to the latest -CURRENT code. All went fine, but one thing bothers me. This box bears Asus P5Q Pro mobo, with the following onboard NIC: ale0@pci0:2:0:0: class=0x020000 card=0x82261043 chip=0x10261969 rev=0xb0 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR8121/AR8113/AR8114 Gigabit or Fast Ethernet' class = network subclass = ethernet According the the specs, it should be GigE. In fact, when plugged into a capable switch, it displays "green" (gig) status (same on the switch), but once being initialized by the kernel, it downgrades to yellowish 100mbps (real speeds agree). I'm not sure why it happens; maybe it's somehow related to a handful of those "ale0: link state changed to DOWN/UP" flip-flops I see in dmesg(8), before it can finally obtain DHCP lease? I remember these adapters had problems in the past, like infamous "Corrupted MAC on input" disconnect messages, but I don't recall that I could not use it in GigE mode. Anything I can do about it? Googling did not help much: most reports date back to ca. 2009, and apparently were ironed out in later revisions (e.g. selectively disabling checksum offloading). Thanks, ./danfe