[Bug 234766] em(4) Intel 82579LM MSI-X problem
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jan 8 18:44:51 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234766
Bug ID: 234766
Summary: em(4) Intel 82579LM MSI-X problem
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: PopularMoment at protonmail.com
12.0-RELEASE-p1 on a Supermicro X9SCM-F using the on board em0 which is a
82579LM.
MSI-X is enabled by default despite the driver initialisation showing a problem
with MSI-X: "Unable to map MSIX table"
em0: <Intel(R) PRO/1000 Network Connection> port 0xf020-0xf03f mem
0xfbb00000-0xfbb1ffff,0xfbb24000-0xfbb24fff irq 20 at device 25.0 on pci0
em0: attach_pre capping queues at 1
em0: using 1024 tx descriptors and 1024 rx descriptors
em0: msix_init qsets capped at 1
em0: Unable to map MSIX table
em0: Using an MSI interrupt
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
# pciconf -lv
[...]
em0 at pci0:0:25:0: class=0x020000 card=0x150215d9 chip=0x15028086 rev=0x05
hdr=0x00
vendor = 'Intel Corporation'
device = '82579LM Gigabit Network Connection (Lewisville)'
class = network
subclass = ethernet
This eventually leads to the interface going down, yet the box remains up and
responsive, with the only recourse to restoring the network being a reboot.
em0: TX(0) desc avail = 42, pidx = 988
em0: link state changed to DOWN
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
[...]
em0: TX(0) desc avail = 1024, pidx = 0
The workaround appears to be to disable MSI-X:
# sysctl dev.em.0.iflib.disable_msix=0
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list