[Bug 234570] em(4) regression in 12.0-STABLE

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234570

            Bug ID: 234570
           Summary: em(4) regression in 12.0-STABLE
           Product: Base System
           Version: 12.0-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: zarychtam at plan-b.pwste.edu.pl

I have recently upgraded one box running 11.2-STABLE to 12.0-STABLE, but
unexpectedly occurred some issues regarding em(4) NIC.

Wake on LAN still works, but NIC is deaf after resume regardless the machine
was woken up by NIC itself or ACPI button. After resume the switch reports 1000
link, but when the port is cycled down/up the link doesn't bring up any more.
No problems are reported in the kernel message buffer.

The second issue comes from constant number of TX/RX queues. Both loader
tunables: hw.em.txd and hw.em.rxd are silently ignored and there are always
"em0: netmap queues/slots: TX 1/1024, RX 1/1024"

Also, the opportunity to enable "options EM_MULTIQUEUE" in the kernel config
file has been depreciated which seems like planned degradation of performance
for this popular NIC.

The affected computer has this network card:

em0 at pci0:0:25:0:        class=0x020000 card=0x1905103c chip=0x153a8086 rev=0x05
hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Connection I217-LM'
    class      = network
    subclass   = ethernet
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 13[e0] = PCI Advanced Features: FLR TP

Suspend/resume and wake on LAN worked fine in 11.2-STABLE, not counting the
fact that the machine was able to suspended only once. Suspending after resume
worked, but workstation was waking up almost immediately (with "sysctl
dev.em.0.wake=1" set). Next long lasting sleep state was possible only after
reboot.

-- 
You are receiving this mail because:
You are the assignee for the bug.