Date: Thu, 1 Dec 2016 10:53:04 -0700 From: Sean Bruno <sbruno@freebsd.org> To: freebsd-net@freebsd.org Subject: Re: Intel 82567V-2 using em driver, no carrier or constant link-state changes with 1000BaseT Message-ID: <3b590d4f-5eeb-f4f7-8ce5-ee71807d6e14@freebsd.org> In-Reply-To: <CAHSynqbosqKaEtL=k7MHcmjCsoXMmbkjBq=QTE256BwcmuD95A@mail.gmail.com> References: <CAHSynqbosqKaEtL=k7MHcmjCsoXMmbkjBq=QTE256BwcmuD95A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PFOCGjnjAi1KG6vQUNom3O89XpU5GrkQb Content-Type: multipart/mixed; boundary="4pboO0tTiRdMGiP3bvgc6qU9xQ1x0GLH6"; protected-headers="v1" From: Sean Bruno <sbruno@freebsd.org> To: freebsd-net@freebsd.org Message-ID: <3b590d4f-5eeb-f4f7-8ce5-ee71807d6e14@freebsd.org> Subject: Re: Intel 82567V-2 using em driver, no carrier or constant link-state changes with 1000BaseT References: <CAHSynqbosqKaEtL=k7MHcmjCsoXMmbkjBq=QTE256BwcmuD95A@mail.gmail.com> In-Reply-To: <CAHSynqbosqKaEtL=k7MHcmjCsoXMmbkjBq=QTE256BwcmuD95A@mail.gmail.com> --4pboO0tTiRdMGiP3bvgc6qU9xQ1x0GLH6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 11/27/16 12:40, Michael Knap wrote: > Preface: I've been a long-time linux user, and I am enjoying the BSD > experience. For the following scenario, I have reproduced these results= > with 3 or more cables which are known to be good. >=20 > Using FreeBSD 10.3 Stable : > FreeBSD 10.3-STABLE #0 r295946+07c41cd(9.10-STABLE): Wed Nov 9 00:19:2= 5 > UTC 2016 root@gauntlet > :/freenas-9.10-releng/_BE/objs/freenas-9.10-releng/_BE/os/sys/FreeNAS.a= md64 >=20 > Also, this isn't a NIC, per se, as it is onboard, but I will call it a = NIC > or card or whatever. >=20 > Using em driver, though I don't know how to determine a driver version = (if > there is such a thing). >=20 > Basically, the card will not push gigabit, though it will work with > 100BaseTX. However, there seems to be more than just that as the chip-s= et > is advertised as a gigabit Ethernet controller. >=20 > When connected to a 100BaseTX switch, everything is good. Leaving it in= > autodetect mode, and connecting to a 1000baseTX switch (with good CAT6 > cable), the card's link state oscillates from link up and link down: >=20 > Nov 27 13:07:38 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:38 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:41 freenas kernel: em0: link state changed to UP > Nov 27 13:07:41 freenas kernel: em0: link state changed to UP > Nov 27 13:07:41 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:41 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:55 freenas kernel: em0: link state changed to UP > Nov 27 13:07:55 freenas kernel: em0: link state changed to UP > Nov 27 13:07:56 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:56 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:58 freenas kernel: em0: link state changed to UP > Nov 27 13:07:58 freenas kernel: em0: link state changed to UP > Nov 27 13:07:59 freenas kernel: em0: link state changed to DOWN > Nov 27 13:07:59 freenas kernel: em0: link state changed to DOWN > Nov 27 13:08:01 freenas kernel: em0: link state changed to UP > Nov 27 13:08:01 freenas kernel: em0: link state changed to UP > Nov 27 13:08:02 freenas kernel: em0: link state changed to DOWN > Nov 27 13:08:02 freenas kernel: em0: link state changed to DOWN >=20 > If I issue ifconfig em0 media 100baseTX mediaopt full-duplex, then I h= ave > no carrier. > Also, ifconfig em0 media 1000baseT gives no carrier. > However, if I ifconfig em0 media 10baseT, then I can get an active link= =2E >=20 > Interestingly, man em(4) does not claim to support this chipset, though= it > seems that this chipset was once supported in either e1000 or igb for o= lder > freeBSD versions? >=20 > Now, at least from the driver's POV, I should be able to handle gigabit= , as >=20 > ifconfig -m em0 > em0: flags=3D8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 150= 0 > options=3D4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,= WOL_MAGIC,VLAN_HWTSO> > capabilities=3D5399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,= TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO> > ether 00:25:11:59:d4:be > inet 10.42.0.111 netmask 0xffffff00 broadcast 10.42.0.255 > nd6 options=3D9<PERFORMNUD,IFDISABLED> > media: Ethernet 10baseT/UTP (10baseT/UTP <half-duplex>) > status: active > supported media: > media autoselect > media 1000baseT > media 1000baseT mediaopt full-duplex > media 100baseTX mediaopt full-duplex > media 100baseTX > media 10baseT/UTP mediaopt full-duplex > media 10baseT/UTP >=20 > However when connected to gigabit switch, any explicit declaration of m= edia > fails except for 10baseT, even the autoselect declaration fails with no= > carrier. >=20 > But remember, 100baseTX works out of the box on a 100Mbit switch. >=20 > So, those more experienced, can you shed some light on what is happenin= g? > I'm especially interested in the man em(4) result even though the chips= et > has been supported in the past, and intel does provide drivers for this= > chipset, though I'm not sure if I could compile them or not. BTW, my > switches are only consumer grade, unmanaged. Is that where I'm stuck? >=20 > Thanks for such an awesome license, operating system, and community. > _______________________________________________ Just so I know which device this specifically is, can you post "pciconf -lvbc" to a pastebin or dpaste type site so we can review which driver this should be using. Linux seems to use igb(4) for this instead of em(4= ). sean --4pboO0tTiRdMGiP3bvgc6qU9xQ1x0GLH6-- --PFOCGjnjAi1KG6vQUNom3O89XpU5GrkQb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJYQGOAXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kz74IAK6IOD9D4gy/3DIQUPj0S4z7 SiCk53QF0SSoITCSptF1XibqvlPGAYdJnHKtZe4l+mKYs5gDZx+9WVVdzWV8rYqw BukK4OC4qepdvl+7XuFib+cHSy64XCoAEs/NLk8is/2kx7xcpLceWXLsE59cmHOP +JJ35h/E4nx3YP0BOo6Mij0cThDARskep9f4YBruou9D5OeUwACdATvWmFnCle2E 7d6PNcSoEsHpdflQIPNs48HCGtZ+OamoSv4hL4nv+Cr3EMsInvNw1GFltUiG2GDH sZgGaDZ3oJSNF6qet2aryS0F/kbA2tqxOYMdv6I2a5UqlFdmKy5rHRYV5kw5lJM= =IIen -----END PGP SIGNATURE----- --PFOCGjnjAi1KG6vQUNom3O89XpU5GrkQb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3b590d4f-5eeb-f4f7-8ce5-ee71807d6e14>