[DPDK/bnxt] Issues starting bnxt on an Arm server

[Thierry Herbelot <thierry.herbelot@6wind.com>]

Hello,

I would like to start testpmd with bnxt ports, when running on an Arm 
server.

This is the log at startup (with testpmd from DPDK v20.11.4):

dpdk-devbind.py -b vfio-pci 03:00.0
dpdk-devbind.py -b vfio-pci 03:00.1

dpdk-testpmd -l 1,3,5 --main-lcore 1
EAL: Detected 48 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-16777216kB
EAL: No available hugepages reported in hugepages-2048kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL:   using IOMMU type 8 (No-IOMMU)
EAL: Probe PCI driver: net_bnxt (14e4:1750) device: 0000:03:00.0 (socket 0)
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x0000, seq_id 0
bnxt_hwrm_ver_get(): failed rc:-110
ethdev initialisation failed
EAL: Releasing pci mapped resource for 0000:03:00.0
EAL: Calling pci_unmap_resource for 0000:03:00.0 at 0x4180000000
EAL: Calling pci_unmap_resource for 0000:03:00.0 at 0x4180010000
EAL: Requested device 0000:03:00.0 cannot be used
EAL:   using IOMMU type 8 (No-IOMMU)
EAL: Probe PCI driver: net_bnxt (14e4:1750) device: 0000:03:00.1 (socket 0)
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x0000, seq_id 0
bnxt_hwrm_ver_get(): failed rc:-110
ethdev initialisation failed
EAL: Releasing pci mapped resource for 0000:03:00.1
EAL: Calling pci_unmap_resource for 0000:03:00.1 at 0x4180110000
EAL: Calling pci_unmap_resource for 0000:03:00.1 at 0x4180120000
EAL: Requested device 0000:03:00.1 cannot be used

The server is running Redhat-8 with the following kernel:
4.18.0-348.7.1.el8_5.aarch64 #1 SMP Wed Dec 8 21:35:15 EST 2021

As the IOMMU on this server is not working, the kernel is started with 
the following option:
vfio.enable_unsafe_noiommu_mode=1

A similar testpmd log is obtained with DPDK v21.11.0.


Is this a know issue ?

	Thanks

	Thierry Herbelot

PS: a similar error is seen for the Ethernet ports, when handled by the 
kernel:
dmesg|grep bnxt
[   57.823746] bnxt_en 0000:03:00.0 (unnamed net_device) 
(uninitialized): Error (timeout: 500015) msg {0x0 0x0} len:0
[   59.202255] bnxt_en: probe of 0000:03:00.0 failed with error -16
[   60.641519] bnxt_en 0000:03:00.1 (unnamed net_device) 
(uninitialized): Error (timeout: 500015) msg {0x0 0x0} len:0
[   61.502237] bnxt_en: probe of 0000:03:00.1 failed with error -16


-- 
Thierry Herbelot
Senior Software Engineer
Tel: +33 1 39 30 92 61
http://www.6wind.com/

Follow us:
https://www.linkedin.com/company/6wind/
https://twitter.com/6WINDsoftware
https://www.youtube.com/user/6windsoftware