[Bug 219428] em network driver broken in current
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Feb 19 20:40:48 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428
patpro <freebsdbug at patpro.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |freebsdbug at patpro.net
--- Comment #17 from patpro <freebsdbug at patpro.net> ---
Hi,
I'm experiencing this bug on:
FreeBSD 12.0-RELEASE-p3 GENERIC amd64
CPU: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz (2793.72-MHz K8-class CPU)
em0: <Intel(R) PRO/1000 Network Connection> port 0xf080-0xf09f mem
0xf7e00000-0xf7e1ffff,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
em1: <Intel(R) PRO/1000 Network Connection> port 0xe000-0xe01f mem
0xf7c00000-0xf7c1ffff,0xf7c20000-0xf7c23fff irq 18 at device 0.0 on pci3
em1: attach_pre capping queues at 2
Current cap: 0x460b
em1: using 1024 tx descriptors and 1024 rx descriptors
em1: msix_init qsets capped at 2
em1: pxm cpus: 2 queue msgs: 4 admincnt: 1
em1: using 2 rx queues 2 tx queues
em1: Using MSIX interrupts with 3 vectors
em1: allocated for 2 tx_queues
em1: allocated for 2 rx_queues
em1: Ethernet address: 70:54:d2:45:71:41
em1: netmap queues/slots: TX 2/1024, RX 2/1024
em1: TX(1) desc avail = 41, pidx = 179
em1: link state changed to DOWN
em1: TX(1) desc avail = 1024, pidx = 0
em1: TX(1) desc avail = 1024, pidx = 0
em1: TX(1) desc avail = 1024, pidx = 0
...
It's only fixed by a reboot.
How can I know if the fixes mentioned here are present in 12.0-RELEASE-p3 or if
I'll have to wait for p4 or more ?
thanks
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-net
mailing list