Hello Michal,
> I’m running 12-STABLE. Is this a hardware related or possibly a driver
bug?
This is probably a driver / module bug.
[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.
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.
Hope this helps,
Richard Gallamore
On Thu, Nov 21, 2019 at 3:53 AM Michal Vančo via freebsd-stable <
freebsd-sta...@freebsd.org> wrote:
> Hi,
>
> I’m trying to get SR-IOV working with my two port Intel 10G NIC:
>
> ix0@pci0:3:0:0: class=0x020000 card=0x15ad15d9 chip=0x15ad8086 rev=0x00
> hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
> class = network
> subclass = ethernet
> ix1@pci0:3:0:1: class=0x020000 card=0x15ad15d9 chip=0x15ad8086 rev=0x00
> hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
> class = network
> subclass = ethernet
>
> with this iovctl config:
>
> # cat /etc/iovctl_ix1.conf
> PF {
> device: "ix1";
> num_vfs: 4;
> }
>
> I get 4 PCI devices created:
>
> none57@pci0:3:0:129: class=0x020000 card=0x15ad15d9 chip=0x15a88086
> rev=0x00 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Ethernet Connection X552 Virtual Function'
> class = network
> subclass = ethernet
> none58@pci0:3:0:131: class=0x020000 card=0x15ad15d9 chip=0x15a88086
> rev=0x00 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Ethernet Connection X552 Virtual Function'
> class = network
> subclass = ethernet
> none59@pci0:3:0:133: class=0x020000 card=0x15ad15d9 chip=0x15a88086
> rev=0x00 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Ethernet Connection X552 Virtual Function'
> class = network
> subclass = ethernet
> none60@pci0:3:0:135: class=0x020000 card=0x15ad15d9 chip=0x15a88086
> rev=0x00 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'Ethernet Connection X552 Virtual Function'
> class = network
> subclass = ethernet
>
> But the driver fails to attach with following errors:
>
> 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
>
> I’m running 12-STABLE. Is this a hardware related or possibly a driver bug?
>
> regards
> Michal
>
> _______________________________________________
> freebsd-sta...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
