[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 06:20:10 UTC 2019


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

            Bug ID: 240658
           Summary: iflib: Some if_igb(4) devices don't recognize/report
                    carrier loss.
           Product: Base System
           Version: 12.0-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: bugzilla.freebsd at omnilan.de

Hello,

reported back in May 2018 with a Clarkville MAC:
https://lists.freebsd.org/pipermail/freebsd-net/2018-May/050497.html

Currently I see this again in 12.1-pro with Powerville (i211), while other
if_igb(4) NICs are not affected (i350).

I don't have a i217 handy to verify if this bug reoccured, or if my "not
reproducable anymore" was simply wrong.

Can anybody remember when/who worked on that issue?

This is a major issue, since if_lagg(4) clones depend on the link state
information and pulling a cable leads to interrupted communication – the
opposite of what if_lagg(4) should provide! i211 is a widely used on-board
server nic, so most likely many were affected by this issue if shipped with
12.1.

Thanks,

-Harry

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list