From owner-freebsd-net@freebsd.org Thu Dec 1 20:08:23 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCB72C61412 for ; Thu, 1 Dec 2016 20:08:23 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ORSMGA102.jf.intel.com", Issuer "Intel External Issuing CA 6A" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C7B9147A; Thu, 1 Dec 2016 20:08:23 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 01 Dec 2016 12:07:14 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,726,1477983600"; d="scan'208";a="12333394" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by orsmga002.jf.intel.com with ESMTP; 01 Dec 2016 12:07:14 -0800 Received: from orsmsx162.amr.corp.intel.com (10.22.240.85) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 1 Dec 2016 12:07:14 -0800 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.190]) by ORSMSX162.amr.corp.intel.com ([10.22.240.85]) with mapi id 14.03.0248.002; Thu, 1 Dec 2016 12:07:09 -0800 From: "Pieper, Jeffrey E" To: Sean Bruno , "freebsd-net@freebsd.org" Subject: RE: Intel 82567V-2 using em driver, no carrier or constant link-state changes with 1000BaseT Thread-Topic: Intel 82567V-2 using em driver, no carrier or constant link-state changes with 1000BaseT Thread-Index: AQHSS/vQj5igiKbtkUqEOjpdei6LvKDzhGig Date: Thu, 1 Dec 2016 20:07:08 +0000 Message-ID: <2A35EA60C3C77D438915767F458D656883995CC2@ORSMSX111.amr.corp.intel.com> References: <3b590d4f-5eeb-f4f7-8ce5-ee71807d6e14@freebsd.org> In-Reply-To: <3b590d4f-5eeb-f4f7-8ce5-ee71807d6e14@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNWRjNzk1YzgtNjQ1OC00MTRlLWI4MzctYjRmMjAxYTI3YTUyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkIyRXhIZCtid1dGNklPZlp3T1g2andRS290bUFZM2VOZEdrdXY1QkxSdDQ9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2016 20:08:23 -0000 -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] = On Behalf Of Sean Bruno Sent: Thursday, December 01, 2016 9:53 AM To: freebsd-net@freebsd.org Subject: Re: Intel 82567V-2 using em driver, no carrier or constant link-st= ate changes with 1000BaseT 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:25 > UTC 2016 root@gauntlet > :/freenas-9.10-releng/_BE/objs/freenas-9.10-releng/_BE/os/sys/FreeNAS.amd= 64 >=20 > Also, this isn't a NIC, per se, as it is onboard, but I will call it a NI= C > or card or whatever. >=20 > Using em driver, though I don't know how to determine a driver version (i= f > 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-set > 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 hav= e > no carrier. > Also, ifconfig em0 media 1000baseT gives no carrier. > However, if I ifconfig em0 media 10baseT, then I can get an active link. >=20 > Interestingly, man em(4) does not claim to support this chipset, though i= t > seems that this chipset was once supported in either e1000 or igb for old= er > 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 metric 0 mtu 1500 > options=3D4219b > capabilities=3D5399b > ether 00:25:11:59:d4:be > inet 10.42.0.111 netmask 0xffffff00 broadcast 10.42.0.255 > nd6 options=3D9 > media: Ethernet 10baseT/UTP (10baseT/UTP ) > 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 med= ia > 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 happening? > I'm especially interested in the man em(4) result even though the chipset > 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 Sean, This is a client (em) part, and should be 10CE (Boazman/Boulder Creek). Jeff