[Bug 240658] iflib: Some if_igb(4) devices don't recognize/report carrier loss.

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Sep 18 07:25:18 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240658

--- Comment #1 from Harald Schmalzbauer <bugzilla.freebsd at 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.


More information about the freebsd-bugs mailing list