From owner-freebsd-bugs@freebsd.org Wed Jan 23 10:09:48 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE22C14C1624 for ; Wed, 23 Jan 2019 10:09:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 495656C4E5 for ; Wed, 23 Jan 2019 10:09:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0C82014C1623; Wed, 23 Jan 2019 10:09:48 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE1B514C1622 for ; Wed, 23 Jan 2019 10:09:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76EA56C4E2 for ; Wed, 23 Jan 2019 10:09:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A56CCAEF for ; Wed, 23 Jan 2019 10:09:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0NA9k8U062566 for ; Wed, 23 Jan 2019 10:09:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0NA9k9s062565 for bugs@FreeBSD.org; Wed, 23 Jan 2019 10:09:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235147] em(4) driver not working for Intel 82583V Gigabit chip Date: Wed, 23 Jan 2019 10:09:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kumba@gentoo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2019 10:09:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235147 Bug ID: 235147 Summary: em(4) driver not working for Intel 82583V Gigabit chip Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: kumba@gentoo.org Trying to load FreeBSD 12.0-RELEASE on a small, six-port firewall appliance= , a Protectli FW6A (https://protectli.com/product/fw6a/). The device's six por= ts are powered by Intel's 82583V gigabit chipset, and supposed to be supported= by the em(4) driver. I've opened a ticket with Protectli support, and they ha= ve confirmed that 11.2-RELEASE will work, but have verified my observation that 12.0-RELEASE does not. My suspicion is this is a regression from the iflib updates done between 11.2 and 12.0. I've tried a couple of things found in other bugs for the em(4) driver, including disabling TSO, several sysctl tweakables, disabling MSI-X, differ= ent ethernet cables, different ports, etc. Nothing seems to work. Also tried forcing the igb(4) driver, to see if that would pick the ports up, but no g= o on that. Both the em(4) and igb(4) man pages say they can support the 82580 chipsets. The port will take an IP address assigned statically, but cannot look one up via DHCP. It does seem capable of seeing ARP "Who am I?" requests, but can= not see the responses and does not update the ARP tables w/ new MAC addresses, = even after fresh ping attempts (MAC and IPs below redacted). It doesn't appear = to process any other ethertype protocol at all outside of ARP. Though, I have= not verified that via tcpdump real well yet. # arp -a ? (192.168.w.x) at xx:xx:xx:xx:xx:xx on em0 permanent [ethernet] ? (192.168.w.y) at (incomplete) on em0 expired [ethernet] ? (192.168.w.z) at (incomplete) on em0 expired [ethernet] Some additional info from various utilities, with addresses masked: # ifconfig em0 em0: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3D81249b ether xx:xx:xx:xx:xx:xx inet 192.168.w.x netmask 0xffffff00 broadcast 192.168.w.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=3D29 dmesg: pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 em0: port 0xe000-0xe01f mem 0xdfe00000-0xdfe1ffff,0xdfe20000-0xdfe23fff irq 16 at device 0.0 on pci1 em0: attach_pre capping queues at 1 em0: using 1024 tx descriptors and 1024 rx descriptors em0: msix_init qsets capped at 1 em0: pxm cpus: 2 queue msgs: 6 admincnt: 1 em0: using 1 rx queues 1 tx queues em0: Using MSIX interrupts with 2 vectors em0: allocated for 1 tx_queues em0: allocated for 1 rx_queues em0: Ethernet address: xx:xx:xx:xx:xx:xx em0: netmap queues/slots: TX 1/1024, RX 1/1024 ((repeat five more times to em5) em0: link state changed to UP If any additional information is needed to debug this, please let me know. --=20 You are receiving this mail because: You are the assignee for the bug.=