Date: Mon, 16 Jan 2017 14:19:11 -0700 From: Sean Bruno <sbruno@freebsd.org> To: Alan Somers <asomers@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: igb is broken, even across reboots, at r312294 Message-ID: <99f68d7d-94b2-f56b-f44c-15b4310e89ca@freebsd.org> In-Reply-To: <CAOtMX2j=ML1r02=h2j26syGF06dZzo%2BM9BbgdCZ623uqO5oK9g@mail.gmail.com> References: <CAOtMX2j=ML1r02=h2j26syGF06dZzo%2BM9BbgdCZ623uqO5oK9g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wOTh4dmbBvsbbHpGc9l8BucSmtF6J7XX1 Content-Type: multipart/mixed; boundary="Jhx2pAkuKNA6MUE1xJwDbVD438oSrpOCX"; protected-headers="v1" From: Sean Bruno <sbruno@freebsd.org> To: Alan Somers <asomers@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Message-ID: <99f68d7d-94b2-f56b-f44c-15b4310e89ca@freebsd.org> Subject: Re: igb is broken, even across reboots, at r312294 References: <CAOtMX2j=ML1r02=h2j26syGF06dZzo+M9BbgdCZ623uqO5oK9g@mail.gmail.com> In-Reply-To: <CAOtMX2j=ML1r02=h2j26syGF06dZzo+M9BbgdCZ623uqO5oK9g@mail.gmail.com> --Jhx2pAkuKNA6MUE1xJwDbVD438oSrpOCX Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/16/17 13:52, Alan Somers wrote: > Today I updated my machine from 311787 to 312294. After the update, > my igb ports can pass no traffic. If I reboot into kernel.old, they > still can't pass any traffic. They won't even work in the PXE ROM. I > have to power off, pull the power cables, then boot into kernel.old > before they'll work. This behavior is repeatable. >=20 > $ pciconf -lv > ... > igb0@pci0:1:0:0: class=3D0x020000 card=3D0x34dc8086 chip=3D0x10a= 78086 rev=3D0x02 > hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82575EB Gigabit Network Connection' > class =3D network > subclass =3D ethernet > igb1@pci0:1:0:1: class=3D0x020000 card=3D0x34dc8086 chip=3D0x10a= 78086 > rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82575EB Gigabit Network Connection' > class =3D network > subclass =3D ethernet > ... >=20 > $ dmesg # on 311787, it's identical whether or not the igb ports are wo= rking > ... > igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port > 0x2020-0x203f mem 0xb1b20000-0xb1b3ffff,0xb1b44000-0xb1b47fff irq 40 > at device 0.0 on pci1 > igb0: Using MSIX interrupts with 5 vectors > igb0: Ethernet address: 00:1e:67:25:71:bc > igb0: Bound queue 0 to cpu 0 > igb0: Bound queue 1 to cpu 1 > igb0: Bound queue 2 to cpu 2 > igb0: Bound queue 3 to cpu 3 > igb0: netmap queues/slots: TX 4/1024, RX 4/1024 > igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port > 0x2000-0x201f mem 0xb1b00000-0xb1b1ffff,0xb1b40000-0xb1b43fff irq 28 > at device 0.1 on pci1 > igb1: Using MSIX interrupts with 5 vectors > igb1: Ethernet address: 00:1e:67:25:71:bd > igb1: Bound queue 0 to cpu 4 > igb1: Bound queue 1 to cpu 5 > igb1: Bound queue 2 to cpu 6 > igb1: Bound queue 3 to cpu 7 > igb1: netmap queues/slots: TX 4/1024, RX 4/1024 > ... >=20 > $ dmesg # on 312294, when the igb ports are not working > ... > igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port > 0x2020-0x203f mem 0xb1b20000-0xb1b3ffff,0xb1b44000-0xb1b47fff irq 40 > at device 0.0 on pci1 > igb0: attach_pre capping queues at 4 > igb0: using 1024 tx descriptors and 1024 rx descriptors > igb0: msix_init qsets capped at 4 > igb0: pxm cpus: 8 queue msgs: 9 admincnt: 1 > igb0: using 4 rx queues 4 tx queues > igb0: Using MSIX interrupts with 5 vectors > igb0: allocated for 4 tx_queues > igb0: allocated for 4 rx_queues > igb0: Ethernet address: 00:1e:67:25:71:bc > igb0: netmap queues/slots: TX 4/1024, RX 4/1024 > igb1: <Intel(R) PRO/1000 PCI-Express Network Driver> port > 0x2000-0x201f mem 0xb1b00000-0xb1b1ffff,0xb1b40000-0xb1b43fff irq 28 > at device 0.1 on pci1 > igb1: attach_pre capping queues at 4 > igb1: using 1024 tx descriptors and 1024 rx descriptors > igb1: msix_init qsets capped at 4 > igb1: pxm cpus: 8 queue msgs: 9 admincnt: 1 > igb1: using 4 rx queues 4 tx queues > igb1: Using MSIX interrupts with 5 vectors > igb1: allocated for 4 tx_queues > igb1: allocated for 4 rx_queues > igb1: Ethernet address: 00:1e:67:25:71:bd > igb1: netmap queues/slots: TX 4/1024, RX 4/1024 > ... >=20 > Any ideas? >=20 > -Alan >=20 Yeah, fighting with EARLY_AP_STARTUP with regards to initialization of the interfaces. em(4) seems to be ok with my change today, but that change makes igb(4) *very* angry. I'm aware and trying to find a happy medium. sean --Jhx2pAkuKNA6MUE1xJwDbVD438oSrpOCX-- --wOTh4dmbBvsbbHpGc9l8BucSmtF6J7XX1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEuq1GMucSHejSCZfdEgHvyh5yfmQFAlh9OM9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJB QUQ0NjMyRTcxMjFERThEMjA5OTdERDEyMDFFRkNBMUU3MjdFNjQACgkQEgHvyh5y fmS0BwgAhnywDjPKgOJKZrHqYegYuT+jdWsp0JW+vtxpcEByX6kNolWMC1zp72xG 5MOxNoH1FF1dfmv6W+QPhcSgbvq7tSDScJGYuZ+kXc/LWL5pD1c/Pfyyj1uVYo5F 30J6WEuNSLV8sWr/lKP8993JyturjtyViK9i13FqEBi5hNR0AJG3m6GESONID1Yf eMeywwmVuaFGOI+TvRo9xMU383KczoJdK/0ZSnD9InEn52J7i2VJuxebfsLXRlVp UCMvr9zUmyxkTn42Xpes8Htljak3qixjTyRoGav5OsQmmuyft67u4qwfUb1qspC5 UYnTBeTH1OuEEIE4H3gOSAGsHD6KMA== =dDqm -----END PGP SIGNATURE----- --wOTh4dmbBvsbbHpGc9l8BucSmtF6J7XX1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99f68d7d-94b2-f56b-f44c-15b4310e89ca>