[Bug 211062] [ixv] sr-iov virtual function driver fails to attach

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Dec 22 02:13:14 UTC 2017


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

--- Comment #10 from Richard Gallamore <ultima at freebsd.org> ---
(In reply to Piotr Pietruszewski from comment #9)
Hello Piotr,

Thank you very much for the link. After compiling and installing the driver
everything appears to work though I have noticed an errors, i'm not sure if it
is a false positive and also I think the vf is short by one. I have done basic
testing (pinging) on the vfs and seems to work fine.

Setting hw.ix.num_queues seems to no longer matter so I removed it from
/boot/loader.conf. I'm not sure if this was intentional. One error I found so
far:
Dec 21 15:50:42 S1 kernel: ix1: CRITICAL: ECC ERROR!!  Please Reboot!!

Not sure if its a false positive. Seems to happen after the 3rd invoke of
iovctl after reboot, but not entirely sure of the trigger.

64 vfs per port should be available, However, vfs <= 63 everything appeared
normal other than the occasional error previously mentioned.

vfs >= 64 will return error:
iovctl: Failed to configure SR-IOV: No space left on device.

64 is supposed to be the max vfs or am I mistaken? or is the first interface
(ix1) count as one of the vfs?

FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r327068: Thu Dec 21 13:00:34
PST 2017

# cat /boot/loader.conf
if_ix_load="YES"

# cat /etc/iovctl.conf
PF {
        device : ix1;
        num_vfs : 32;
}

DEFAULT {
        passthrough : true;
}
VF-0 {
        passthrough : false;
}
VF-1 {
        passthrough : false;
}

It would be nice to get this in head but after seeing r327031[1], I don't see
this happening anytime soon.

Also want to mention, tested head driver(4.0.0-k) before 3.2.17 and sr-iov is
returning the similar/same errors mentioned in earlier posts on this thread.

[1] https://svnweb.freebsd.org/base?view=revision&revision=327031

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-net mailing list