Date: Wed, 11 Dec 2019 13:40:29 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 236724] igb(4): Interfaces fail to switch active to inactive state Message-ID: <bug-236724-7501-qEYojG7SUx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236724-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-236724-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=3D236724 Vin=C3=ADcius Zavam <egypcio@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egypcio@FreeBSD.org --- Comment #20 from Vin=C3=ADcius Zavam <egypcio@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=3D0x020000 rev=3D0x01 hdr= =3D0x00 vendor=3D0x8086 device=3D0x1521 subvendor=3D0x8086 subdevice=3D0x0002); - live image (https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/Fre= eBSD-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 fr= om the BIOS I should check in a few. =3D=3D=3D=3D=3D igb0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=3D4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS= UM,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=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> igb1: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=3D4e507bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCS= UM,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=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> =3D=3D=3D=3D=3D 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`) =3D=3D=3D=3D=3D bge0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=3Dc019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN= _HWTSO,LINKSTATE> ether 4c:d9:8f:8f:11:9a media: Ethernet autoselect nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> bge1: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=3Dc019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN= _HWTSO,LINKSTATE> ether 4c:d9:8f:8f:11:9b media: Ethernet autoselect nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> =3D=3D=3D=3D=3D --=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-236724-7501-qEYojG7SUx>