Date: Tue, 24 Sep 2019 17:22:04 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report carrier loss. Message-ID: <bug-240658-7501-KTdX8fXjpb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240658-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-240658-7501@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=3D240658 Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |In Progress Resolution|DUPLICATE |--- --- Comment #4 from Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> --- Initially, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239240 descr= ibes a different issue and I'd like to keep that separate, although John Delano ad= ded comment #3, where he mentions the same link state issue. But the proposed f= ix indicates this is an independent issue! The proposed phabriactor patch in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239240#c13 (https://reviews.freebsd.org/D21769) doens't fix the problem. There's progress though: After once marking the interface down and up again, the link state correctly changes from there on. But right after loading the kernel module, link state still doesn't change when physical connection was lost (repeatedly won't change, unless you manually down/up). Tested with 12.1-beta1, D21769+D21712 and i210, i350, 82576 (all hw.mac.type igb ) and 82574L (em) - consistently the same behaviour. Thanks, -Harry --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240658-7501-KTdX8fXjpb>