Date: Wed, 18 Sep 2019 07:25:18 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 240658] iflib: Some if_igb(4) devices don't recognize/report carrier loss. Message-ID: <bug-240658-227-4haoOZINPi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240658-227@https.bugs.freebsd.org/bugzilla/> References: <bug-240658-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=240658 --- Comment #1 from Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> --- Sorry, need to correct myself, much more if_em(4) _and_ if_igb(4) NICs are affected! Took all Intel NICs I have available to verify (in an S1200v3RP server): 82574L (Hartwell) - if_em(4) attaches And the followig if_igb(4) NICs: 82576 (Kawela) i210 (Springville) i350 (StonyLake) According to ifconfig(8), all NICs above report active link state, with the initial media speed, no matter if a cable is attached at all, or the link speed changed (100->1000 but ifconfig still shows 100Base-TX). So currently, with 12.1-PRERELEASE r352354, I can see the issue with all Intel NICs I have available for testing, with one exception: On a different machine with on-board i217-V (Clarkville, the one I reported in my initial post), the link state swiftly and correctly changes. Unfortunately I won't find time to look into the svn hisroty to see if somebody fixed i217 back then or inspect anything in more detail – for the next few weeks at least :-( Hope this can be fixed before 12.1 ships. Thanks, -harry -- 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-240658-227-4haoOZINPi>