Date: Thu, 08 Jan 2009 23:00:18 +0100 From: Christian Brueffer <brueffer@FreeBSD.org> To: Mars G Miro <spry@anarchy.in.the.ph> Cc: freebsd-stable@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: igb on a Nehalem system, buildworld stats Message-ID: <20090108220018.GB1300@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <f12f408a0901081050p1a8154c5h19035f399944b3fc@mail.gmail.com> References: <f12f408a0901080616t78dded81l979a4ec06de7739f@mail.gmail.com> <2a41acea0901080844y1c2ad632t12aeadfbe9f34d0a@mail.gmail.com> <f12f408a0901081019x2ea4e83i47851fa3ed2a0ae4@mail.gmail.com> <2a41acea0901081033h7db7a1aej8399baf5dcbd270f@mail.gmail.com> <f12f408a0901081050p1a8154c5h19035f399944b3fc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 09, 2009 at 02:50:45AM +0800, Mars G Miro wrote: > On Fri, Jan 9, 2009 at 2:33 AM, Jack Vogel <jfvogel@gmail.com> 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% su= re > > 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 mismatch= es > > on systems that will result in things not working in funny ways. >=20 >=20 > 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 ;-) >=20 >=20 > > > > If you have a back to back connection to another NIC on Port 0, no swit= ch, > > does > > it still autoneg to 100? > > >=20 > I will have do that tomorrow as I am @home now ;-) >=20 > btw, another data point, during sysinstall, we encountered: >=20 > <unknown network interface type> on both the igbs. >=20 This is due to missing a missing device entry in the sysinstall code. Unfortunately there are entries missing for several new drivers, I will commit a patch to fix this soon. Anyway, it shouldn't be related to your problems. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFJZndybHYXjKDtmC0RAgNsAKDCtkQx/JyJMZ9Jj3qOjP1WculyrwCg9pzT 5re4wx0N3yBk5/hW06NTMeg= =aiRE -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090108220018.GB1300>