Date: Thu, 21 Nov 2019 19:10:40 +0100 From: =?utf-8?Q?Michal_Van=C4=8Do?= <michal@microwave.sk> To: Richard Gallamore <ultima@freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: device_attach: ixv0 attach returned 5 Message-ID: <01EC7302-24A6-4441-85A2-4D24C97696ED@microwave.sk> In-Reply-To: <CANJ8om4DdeUFWi86YT5LqRuXYD%2BL8X_0t-uDsp%2B_TB6=NFD0qQ@mail.gmail.com> References: <2D60E558-2F48-40EA-BF0D-C350BD005215@microwave.sk> <CANJ8om4DdeUFWi86YT5LqRuXYD%2BL8X_0t-uDsp%2B_TB6=NFD0qQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well then this is really annoying. I can image few other applications = besides virtualization. Jails using vnet bound to VF instead of epair being one = of=20 examples. Any hope that someone will port the SR-IOV from Intel=E2=80=99s = code into the base driver on foreseeable future? regards Michal > On 21 Nov 2019, at 18:52, Richard Gallamore <ultima@freebsd.org> = wrote: >=20 > Hello Michal, >=20 >> I=E2=80=99m running 12-STABLE. Is this a hardware related or possibly = a driver > bug? > This is probably a driver / module bug. >=20 > [1] is a bug on this issue, that I opened some years ago. The last = time > I tested the sr-iov functionality it was working if you compile the = intel > module with sr-iov support enabled but not with the base module. This > was probably a couple years ago though and on 12-CURRENT before > 12 was released. >=20 > Personally I suggest you just avoid sr-iov though and use bridges. = sr-iov > was > a cool idea but it just failed to get an attraction. Probably several > reasons > for this, based on my experience I would say the primary reason is = because > its designed use case is for virtualization, and if you do use this = for > virtualization, you trade the ability to do live migrations due to = using > physical hardware. >=20 > Hope this helps, > Richard Gallamore >=20 > On Thu, Nov 21, 2019 at 3:53 AM Michal Van=C4=8Do via freebsd-stable < > freebsd-stable@freebsd.org> wrote: >=20 >> Hi, >>=20 >> I=E2=80=99m trying to get SR-IOV working with my two port Intel 10G = NIC: >>=20 >> ix0@pci0:3:0:0: class=3D0x020000 card=3D0x15ad15d9 chip=3D0x15ad8086 = rev=3D0x00 >> hdr=3D0x00 >> vendor =3D 'Intel Corporation' >> device =3D 'Ethernet Connection X552/X557-AT 10GBASE-T' >> class =3D network >> subclass =3D ethernet >> ix1@pci0:3:0:1: class=3D0x020000 card=3D0x15ad15d9 chip=3D0x15ad8086 = rev=3D0x00 >> hdr=3D0x00 >> vendor =3D 'Intel Corporation' >> device =3D 'Ethernet Connection X552/X557-AT 10GBASE-T' >> class =3D network >> subclass =3D ethernet >>=20 >> with this iovctl config: >>=20 >> # cat /etc/iovctl_ix1.conf >> PF { >> device: "ix1"; >> num_vfs: 4; >> } >>=20 >> I get 4 PCI devices created: >>=20 >> none57@pci0:3:0:129: class=3D0x020000 card=3D0x15ad15d9 = chip=3D0x15a88086 >> rev=3D0x00 hdr=3D0x00 >> vendor =3D 'Intel Corporation' >> device =3D 'Ethernet Connection X552 Virtual Function' >> class =3D network >> subclass =3D ethernet >> none58@pci0:3:0:131: class=3D0x020000 card=3D0x15ad15d9 = chip=3D0x15a88086 >> rev=3D0x00 hdr=3D0x00 >> vendor =3D 'Intel Corporation' >> device =3D 'Ethernet Connection X552 Virtual Function' >> class =3D network >> subclass =3D ethernet >> none59@pci0:3:0:133: class=3D0x020000 card=3D0x15ad15d9 = chip=3D0x15a88086 >> rev=3D0x00 hdr=3D0x00 >> vendor =3D 'Intel Corporation' >> device =3D 'Ethernet Connection X552 Virtual Function' >> class =3D network >> subclass =3D ethernet >> none60@pci0:3:0:135: class=3D0x020000 card=3D0x15ad15d9 = chip=3D0x15a88086 >> rev=3D0x00 hdr=3D0x00 >> vendor =3D 'Intel Corporation' >> device =3D 'Ethernet Connection X552 Virtual Function' >> class =3D network >> subclass =3D ethernet >>=20 >> But the driver fails to attach with following errors: >>=20 >> ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver> at device = 0.129 >> on pci4 >> ixv0: ...reset_hw() failure: Reset Failed! >> ixv0: IFDI_ATTACH_PRE failed 5 >> device_attach: ixv0 attach returned 5 >> ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver> at device = 0.131 >> on pci4 >> ixv0: ...reset_hw() failure: Reset Failed! >> ixv0: IFDI_ATTACH_PRE failed 5 >> device_attach: ixv0 attach returned 5 >> ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver> at device = 0.133 >> on pci4 >> ixv0: ...reset_hw() failure: Reset Failed! >> ixv0: IFDI_ATTACH_PRE failed 5 >> device_attach: ixv0 attach returned 5 >> ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver> at device = 0.135 >> on pci4 >> ixv0: ...reset_hw() failure: Reset Failed! >> ixv0: IFDI_ATTACH_PRE failed 5 >> device_attach: ixv0 attach returned 5 >>=20 >> I=E2=80=99m running 12-STABLE. Is this a hardware related or possibly = a driver bug? >>=20 >> regards >> Michal >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01EC7302-24A6-4441-85A2-4D24C97696ED>