Hi Aaron, From the log you sent, we can see that the PCI ID of the nic you bind to DPDK is 0000:03:00.0. (This is the entry in the first section, “Network devices using DPDK-compatible driver”). This NIC is not an I40E. It is an IXGBE nic.
However, in the command line that you launch to start testpmd you use a different PCI ID, /tmp/testpmd --log-level=8 -w 05:00.0 …. 05:00.0 is a PCI ID of I40E. (-w stands for whitelist). So in order that it will work with I40E, you should first bind it, using its PCI ID (which is 05:00.0) to DPDK by “dpdk-devbind -b igb_uio 05:00.0” and then launch the same testpmd command that you already used. Since this I40E has two ports, you can also bind the second one to DPDK by “dpdk-devbind -b igb_uio 05:00.1” (You can also unbind 0000:03:00.0 if you don’t need it for any DPDK app by dpdk-devbind -u 0000:03:00.0). If still you get any issues after binding 05:00.0, please post the full log you get when running testpmd. Regards, Rami Rosen From: Aaron Hughes [mailto:[email protected]] Sent: Tuesday, August 14, 2018 16:56 To: Rosen, Rami <[email protected]> Cc: [email protected] Subject: Re: [dpdk-users] Unsupported kernel driver Hi Rami, /tmp/dpdk-devbind.py -s Network devices using DPDK-compatible driver ============================================ 0000:03:00.0 'Ethernet Controller 10-Gigabit X540-AT2 1528' drv=igb_uio unused= Network devices using kernel driver =================================== 0000:03:00.1 'Ethernet Controller 10-Gigabit X540-AT2 1528' if=eth1 drv=ixgbe unused=igb_uio 0000:05:00.0 'Device 1572' if=eth6 drv=i40e unused=igb_uio *Active* 0000:05:00.1 'Device 1572' if=eth7 drv=i40e unused=igb_uio *Active* 0000:08:00.0 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb unused=igb_uio *Active* 0000:08:00.1 'I350 Gigabit Network Connection 1521' if=eth3 drv=igb unused=igb_uio 0000:08:00.2 'I350 Gigabit Network Connection 1521' if=eth4 drv=igb unused=igb_uio 0000:08:00.3 'I350 Gigabit Network Connection 1521' if=eth5 drv=igb unused=igb_uio Other Network devices ===================== <none> Crypto devices using DPDK-compatible driver =========================================== <none> Crypto devices using kernel driver ================================== <none> Other Crypto devices ==================== <none> Eventdev devices using DPDK-compatible driver ============================================= <none> Eventdev devices using kernel driver ==================================== <none> Other Eventdev devices ====================== <none> Mempool devices using DPDK-compatible driver ============================================ <none> Mempool devices using kernel driver =================================== <none> Other Mempool devices ===================== <none> On Tue, Aug 14, 2018 at 6:32 AM Rosen, Rami <[email protected]<mailto:[email protected]>> wrote: Hi Aaron, What does dpdk-17.05/usertools/dpdk-devbind.py -s show ? Regards, Rami Rosen -----Original Message----- From: users [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Aaron Hughes Sent: Tuesday, August 14, 2018 08:54 To: [email protected]<mailto:[email protected]> Subject: [dpdk-users] Unsupported kernel driver I'm having trouble getting testpmd to work with an Intel X710. I'm seeing an unsupported kernel driver error. Based on this page I think I'm using the correct kernel driver: http://doc.dpdk.org/guides/nics/i40e.html#recommended-matching-list Does anyone have any idea what I'm doing wrong? My system info: CentOS release 6.5 (Final) Intel X710 with version 5.05 firmware Kernel Driver: i40e version 1.5.23 (From Intel) DPDK version: 17.05 /tmp/testpmd --log-level=8 -w 05:00.0EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 1 on socket 0 EAL: Detected lcore 2 as core 2 on socket 0 EAL: Detected lcore 3 as core 3 on socket 0 EAL: Detected lcore 4 as core 4 on socket 0 EAL: Detected lcore 5 as core 8 on socket 0 EAL: Detected lcore 6 as core 9 on socket 0 EAL: Detected lcore 7 as core 10 on socket 0 EAL: Detected lcore 8 as core 11 on socket 0 EAL: Detected lcore 9 as core 12 on socket 0 EAL: Detected lcore 10 as core 0 on socket 0 EAL: Detected lcore 11 as core 1 on socket 0 EAL: Detected lcore 12 as core 2 on socket 0 EAL: Detected lcore 13 as core 3 on socket 0 EAL: Detected lcore 14 as core 4 on socket 0 EAL: Detected lcore 15 as core 8 on socket 0 EAL: Detected lcore 16 as core 9 on socket 0 EAL: Detected lcore 17 as core 10 on socket 0 EAL: Detected lcore 18 as core 11 on socket 0 EAL: Detected lcore 19 as core 12 on socket 0 EAL: Support maximum 128 logical core(s) by configuration. EAL: Detected 20 lcore(s) EAL: Setting up physically contiguous memory... EAL: Ask a virtual area of 0x200000 bytes EAL: Virtual area found at 0x7fb9e9400000 (size = 0x200000) EAL: Ask a virtual area of 0x7fc00000 bytes EAL: Virtual area found at 0x7fb969600000 (size = 0x7fc00000) EAL: Ask a virtual area of 0x200000 bytes EAL: Virtual area found at 0x7fb969200000 (size = 0x200000) EAL: Requesting 1024 pages of size 2MB from socket 0 EAL: TSC frequency is ~2394234 KHz EAL: Master lcore 0 is ready (tid=e9afc8c0;cpuset=[0]) EAL: lcore 10 is ready (tid=62df5700;cpuset=[10]) EAL: lcore 2 is ready (tid=67dfd700;cpuset=[2]) EAL: lcore 1 is ready (tid=687fe700;cpuset=[1]) EAL: lcore 18 is ready (tid=5dded700;cpuset=[18]) EAL: lcore 13 is ready (tid=60ff2700;cpuset=[13]) EAL: lcore 3 is ready (tid=673fc700;cpuset=[3]) EAL: lcore 6 is ready (tid=655f9700;cpuset=[6]) EAL: lcore 17 is ready (tid=5e7ee700;cpuset=[17]) EAL: lcore 9 is ready (tid=637f6700;cpuset=[9]) EAL: lcore 12 is ready (tid=619f3700;cpuset=[12]) EAL: lcore 7 is ready (tid=64bf8700;cpuset=[7]) EAL: lcore 4 is ready (tid=669fb700;cpuset=[4]) EAL: lcore 8 is ready (tid=641f7700;cpuset=[8]) EAL: lcore 14 is ready (tid=605f1700;cpuset=[14]) EAL: lcore 19 is ready (tid=5d3ec700;cpuset=[19]) EAL: lcore 16 is ready (tid=5f1ef700;cpuset=[16]) EAL: lcore 5 is ready (tid=65ffa700;cpuset=[5]) EAL: lcore 15 is ready (tid=5fbf0700;cpuset=[15]) EAL: lcore 11 is ready (tid=623f4700;cpuset=[11]) EAL: Driver (net_ark) doesn't match the device EAL: Driver (net_avp) doesn't match the device EAL: Driver (net_bnxt) doesn't match the device EAL: Driver (net_cxgbe) doesn't match the device EAL: Driver (net_e1000_igb) doesn't match the device EAL: Driver (net_e1000_igb_vf) doesn't match the device EAL: Driver (net_e1000_em) doesn't match the device EAL: Driver (net_ena) doesn't match the device EAL: Driver (net_enic) doesn't match the device EAL: Driver (net_fm10k) doesn't match the device EAL: PCI device 0000:05:00.0 on NUMA socket -1 EAL: probe driver: 8086:1572 net_i40e EAL: Not managed by a supported kernel driver, skipped EAL: Driver (net_i40e_vf) doesn't match the device EAL: Driver (net_ixgbe) doesn't match the device EAL: Driver (net_ixgbe_vf) doesn't match the device EAL: Driver (net_liovf) doesn't match the device EAL: Driver (net_nfp) doesn't match the device EAL: Driver (net_qede) doesn't match the device EAL: Driver (net_qede_vf) doesn't match the device EAL: Driver (net_sfc_efx) doesn't match the device EAL: Driver (net_thunderx) doesn't match the device EAL: Driver (net_virtio) doesn't match the device EAL: Driver (net_vmxnet3) doesn't match the device EAL: Driver (event_skeleton_pci) doesn't match the device EAL: Driver (octeontx_ssowvf) doesn't match the device EAL: Driver (octeontx_ssovf) doesn't match the device EAL: No probed ethernet devices
