From owner-freebsd-stable@FreeBSD.ORG Fri Jan 9 08:02:10 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FE071065672 for ; Fri, 9 Jan 2009 08:02:10 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id DB7238FC17 for ; Fri, 9 Jan 2009 08:02:09 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by fg-out-1718.google.com with SMTP id l26so3061320fgb.35 for ; Fri, 09 Jan 2009 00:02:08 -0800 (PST) Received: by 10.86.86.12 with SMTP id j12mr14753945fgb.33.1231488128633; Fri, 09 Jan 2009 00:02:08 -0800 (PST) Received: by 10.86.84.8 with HTTP; Fri, 9 Jan 2009 00:02:08 -0800 (PST) Message-ID: Date: Fri, 9 Jan 2009 16:02:08 +0800 From: "Mars G Miro" To: "Jack Vogel" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0901080844y1c2ad632t12aeadfbe9f34d0a@mail.gmail.com> <2a41acea0901081033h7db7a1aej8399baf5dcbd270f@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: igb on a Nehalem system, buildworld stats 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: Fri, 09 Jan 2009 08:02:10 -0000 On Fri, Jan 9, 2009 at 2:50 AM, Mars G Miro wrote: > On Fri, Jan 9, 2009 at 2:33 AM, Jack Vogel wrote: >> Well, I am at Intel you know, and even we don't seem to have any systems >> with >> 82576 down in my group here. The way link works I can be about 99.9% sure >> in saying its not the driver. Its preproduction so there are lots of >> possibilities, >> and the biggest problem is its going to be difficult to help when I don't >> have any >> such hardware :( >> >> I've heard from the 1G product team that they have seen EEPROM mismatches >> on systems that will result in things not working in funny ways. > > > Jahh, I've seen those but not w/ Intel NICs. I believe it was from > Broadcom on some IBM x3455? (IIRC) and it was indeed quite amusing ;-) > > >> >> If you have a back to back connection to another NIC on Port 0, no switch, >> does >> it still autoneg to 100? >> Connected back to back w/ another box w/ a GigE NIC, it now does 1000baseTX: igb0: flags=8843 metric 0 mtu 1500 options=19b ether 00:30:48:c5:db:e2 inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 inet 192.168.70.2 netmask 0xffffff00 broadcast 192.168.70.255 media: Ethernet autoselect (1000baseTX ) status: active But still not without problems. I hafta ifconfig down/up it several times until I can see the other end. W/c is the same for igb1. > [snip] -- cheers mars