[Bug 290793] iovctl on mlx5en won't work

[email protected]
Newsgroups gmane.os.freebsd.devel.net
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290793

--- Comment #9 from Bjoern A. Zeeb <[email protected]> ---
(In reply to David BOYER from comment #6)

Hi,

thanks for the apparently simple sample.  I am still running into a prereq
problem:

I enabled SR-IOV in BIOS.
I enabled it in the Mellanox Firmware flexboot thingy.
GENERIC has SR-IOV support in it as much as I could see.

# ls -l /dev/iov
ls: /dev/iov: No such file or directory

# iovctl -C -f /etc/iovctl/mce0.conf
iovctl: Could not open device '/dev/iov/mlx5_core0': No such file or directory

What else needs doing to get this?

# pciconf -lBbcevV mlx5_core0
mlx5_core0@pci0:2:0:0:  class=0x020000 rev=0x00 hdr=0x00 vendor=0x15b3
device=0x1013 subvendor=0x15b3 subdevice=0x0008
    vendor     = 'Mellanox Technologies'
    device     = 'MT27700 Family [ConnectX-4]'
    class      = network
    subclass   = ethernet
    bar   [10] = type Prefetchable Memory, range 64, base 0x383ffc000000, size
33554432, enabled
    cap 10[60] = PCI-Express 2 endpoint max data 256(512) FLR NS
                 max read 512
                 link x16(x16) speed 8.0(8.0)
    cap 03[48] = VPD
    cap 11[9c] = MSI-X supports 128 messages, enabled
                 Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
    cap 09[c0] = vendor (length 24)
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    ecap 0003[100] = Serial 1 xxx
    ecap 0001[110] = AER 1 0 fatal 0 non-fatal 1 corrected
    ecap 000e[170] = ARI 1
    ecap 0019[1c0] = PCIe Sec 1 lane errors 0
  PCI-e errors = Correctable Error Detected
                 Unsupported Request Detected
     Corrected = Advisory Non-Fatal Error
    VPD ident  = 'CX416A - ConnectX-4 QSFP'
    VPD ro PN  = 'MCX416A-CCAT         '
    VPD ro EC  = 'A5'
    VPD ro SN  = 'MT1544X0xxxx            '
    VPD ro V0  = 'PCIeGen3 x16    '

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.