[Bug 236724] igb(4): Interfaces fail to switch active to inactive state

[bugzilla-noreply at freebsd.org]

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

Vinícius Zavam <egypcio at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |egypcio at FreeBSD.org

--- Comment #20 from Vinícius Zavam <egypcio at FreeBSD.org> ---
I did see it happening in HEAD (r355121/amd64) during a silly test I was
conducting trying to reproduce bug #239240. should we reopen this issue?

used components to reproduce it;

 - physical hardware
(https://www.dell.com/en-us/work/shop/povw/poweredge-r440);
 - intel i350 gigabit network card [igb] (class=0x020000 rev=0x01 hdr=0x00
vendor=0x8086 device=0x1521 subvendor=0x8086 subdevice=0x0002);
 - live image
(https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20191127-r355121-mini-memstick.img).

how to reproduce;

 - leave NO ethernet cables plugged to the net. card's ports;
 - boot the live image, and choose 'live cd' option (log in as root, of
course);
 - perform an `ifconfig` to get actual status/options of all igb interfaces;
 - plug a cable to the igb interface of your choice (the other end must be
connected to a switch or anything that can trigger layer1 activity);
 - perform an `ifconfig` to get actual status/options of all igb interfaces;
 - unplug the cable;
 - perform an `ifconfig` to get actual status/options of all igb interfaces.

NOTE: after performing an `ifconfig igb0 up` and testing it all again, the
feedback to its physical status are all fine.

* igb0 is the only one showing 'WOL_MAGIC' but that's maybe some setting from
the BIOS I should check in a few.

=====
igb0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
        ether b4:96:91:62:ef:92
        media: Ethernet autoselect
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
igb1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4e507bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
        ether b4:96:91:62:ef:93
        media: Ethernet autoselect
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
=====



MORE ABOUT IT: the odd situation is that we can see "status:" on all intel
interfaces even before performing the very first `ifconfig igb0 up` --- for the
onboard broadcom interfaces, there's no such a thing (all broadcom stay DOWN
and display no "status:" line before performing `ifconfig bge0 up`)

=====
bge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
        ether 4c:d9:8f:8f:11:9a
        media: Ethernet autoselect
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
bge1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
        ether 4c:d9:8f:8f:11:9b
        media: Ethernet autoselect
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
=====

-- 
You are receiving this mail because:
You are on the CC list for the bug.