From owner-freebsd-net@freebsd.org Sun Nov 27 19:40:55 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 046F8C596DA for ; Sun, 27 Nov 2016 19:40:55 +0000 (UTC) (envelope-from michael.j.knap@gmail.com) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4E23D6B for ; Sun, 27 Nov 2016 19:40:54 +0000 (UTC) (envelope-from michael.j.knap@gmail.com) Received: by mail-qk0-x232.google.com with SMTP id x190so121297360qkb.0 for ; Sun, 27 Nov 2016 11:40:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=iekxDbtSJmGMdViPuATstA5kG5kAUf/Cx7y1GKofi8w=; b=Ur+GlDwX229EYYyeBjnjyhVScwH/wWuSpN+1PSttvnzlX/kE3xDi/a/jPcc1ZU2Hus 1I82JYA5VoQDkSaHPEepAUGTK8sXSgWLN2sLMugnaf7OQPwsXWYSAFoYmQKDyfBRY6DH gzCAd4DuLcFQMo8g8aqFoWly1eTxPNpBqvqSrON0y7o61OkrceZpZNOb1R83fAwEugu7 ZZYYaoSQysU8X+lPZqd2f0NWrBZBX5PNttMKZk0Z7CBRORygxUUyF6vI0SaVbf5somPk imUm+3kfAyejzIIqkgjfjur//FzYTLSRaGWcDH8Kg72cwaYSy0Lkuj6krCkYH+6cKYqi nOEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=iekxDbtSJmGMdViPuATstA5kG5kAUf/Cx7y1GKofi8w=; b=QQTZjVPFsDr1dYM7tdMOgqEbTcVrrjLOgOSNDUm7k7JVgK5ZuGkQDpm5OK/NKxz56S 6dgCtJqGBh7ikz13GAZj6k/2WOx9qqlXRpjNKPZrksrnKWGe3UHX1vwpttC03sMnqZZQ UE/v/URWB/TSAqVTXuBICAGQqTbYl1vheI55d5C6PRd4TAeSjrsmjxn/D0XnvdObnJTr 6Qgristk9I60CbRl03GMAa4R1ybA2N4wInUaM4UtPAB5EvNOlNw/LbFxIom5pVDZEn3l vRF/Utfwi+k6ipu9H4VeWnOB/a1R9h+G70p5VqEz9INotubfHPkBRvQu2fw45v4/7NVy HXJg== X-Gm-Message-State: AKaTC014M7IpM6i5SsEw9S3BwdHJJ1Nl61lwEudHYrueMLOom9jxlZUrZpLJLL4lphZTjFeOuyP1v57JCAZX0A== X-Received: by 10.55.17.206 with SMTP id 75mr14565445qkr.10.1480275653706; Sun, 27 Nov 2016 11:40:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.95.112 with HTTP; Sun, 27 Nov 2016 11:40:53 -0800 (PST) From: Michael Knap Date: Sun, 27 Nov 2016 13:40:53 -0600 Message-ID: Subject: Intel 82567V-2 using em driver, no carrier or constant link-state changes with 1000BaseT To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Sun, 27 Nov 2016 19:40:55 -0000 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. 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.amd64 Also, this isn't a NIC, per se, as it is onboard, but I will call it a NIC or card or whatever. Using em driver, though I don't know how to determine a driver version (if there is such a thing). 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. 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: 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 If I issue ifconfig em0 media 100baseTX mediaopt full-duplex, then I have no carrier. Also, ifconfig em0 media 1000baseT gives no carrier. However, if I ifconfig em0 media 10baseT, then I can get an active link. 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 older freeBSD versions? Now, at least from the driver's POV, I should be able to handle gigabit, as ifconfig -m em0 em0: flags=8c02 metric 0 mtu 1500 options=4219b capabilities=5399b ether 00:25:11:59:d4:be inet 10.42.0.111 netmask 0xffffff00 broadcast 10.42.0.255 nd6 options=9 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 However when connected to gigabit switch, any explicit declaration of media fails except for 10baseT, even the autoselect declaration fails with no carrier. But remember, 100baseTX works out of the box on a 100Mbit switch. 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? Thanks for such an awesome license, operating system, and community.