[Bug 231828] em(4) is unusable after suspend/resume
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Sep 30 17:21:47 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231828
Bug ID: 231828
Summary: em(4) is unusable after suspend/resume
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: pete at nomadlogic.org
There are several reports that when using an em(4) device on 12-CURRENT the NIC
is unusable until after a reboot or kld_unload/kld_load of the if_em kernel
module.
upon resume there are messages like this in the dmesg buffer:
in6_purgeaddr: err=65, destination address delete failed
lo0: link state changed to DOWN
lo0: link state changed to UP
Link state changed to down
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
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0
there is a mailing list thread about the issue here:
https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071408.html
my device info via pciconf:
em0 at pci0:0:31:6: class=0x020000 card=0x30d017aa chip=0x15b78086 rev=0x31
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection (2) I219-LM'
class = network
subclass = ethernet
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list