Date: Sun, 20 Jan 2019 11:56:00 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231828] em(4) is unusable after suspend/resume Message-ID: <bug-231828-227-wuMhVbEzka@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231828-227@https.bugs.freebsd.org/bugzilla/> References: <bug-231828-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231828 Chris <freebsdbugs@ontoemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsdbugs@ontoemail.com --- Comment #4 from Chris <freebsdbugs@ontoemail.com> --- Not sure if I should reply to a closed bug. I am unable to use the network after suspend/resume with a 12.0-RELEASE r341666 GENERIC amd64 kernel. Suspend/resume works, except there is no network traffic. ifconfig down/up = does not restore it. There have been times where it did resume properly, but usu= ally does not. dmesg: em0: TX(0) desc avail =3D 1024, pidx =3D 0 em0: TX(0) desc avail =3D 1024, pidx =3D 0 pciconf: em0@pci0:0:31:6: class=3D0x020000 card=3D0x86721043 chip=3D0x15b8808= 6 rev=3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Ethernet Connection (2) I219-V' class =3D network subclass =3D ethernet --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231828-227-wuMhVbEzka>