BTW, here is the output of the dpdk-devbind status. It all looks good to me.
root@irisheyes9-Z240-SFF:~# dpdk-devbind -s Network devices using DPDK-compatible driver ============================================ 0000:03:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1584' drv=vfio-pci unused=i40e 0000:03:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1584' drv=vfio-pci unused=i40e Network devices using kernel driver =================================== 0000:00:1f.6 'Ethernet Connection (2) I219-LM 15b7' if=eno1 drv=e1000e unused=vfio-pci *Active* 0000:03:00.2 'Ethernet Controller XL710 for 40GbE QSFP+ 1584' if=ens4f2 drv=i40e unused=vfio-pci *Active* 0000:03:00.3 'Ethernet Controller XL710 for 40GbE QSFP+ 1584' if=ens4f3 drv=i40e unused=vfio-pci *Active* On Mon, Feb 1, 2021 at 7:51 PM Rob Kossler <[email protected]> wrote: > I'm running as root. Here is the full command I'm using with my N310 and > the first part of the resulting output. Note that the ERROR is now a UHD > generated error message rather than an error message from the DPDK libs. > > One thing I'm looking into is the "vfio-pci" module. The instructions say > to load this via "modprobe vfio-pci" prior to binding the NIC. But, I > didn't have to do this and it seems that this module might now be built-in > such that it is not necessary. In any case, the "dpdk-devbind" seems to > work fine so maybe I am barking up the wrong tree. > > root@irisheyes9-Z240-SFF:~# benchmark_rate --rx_rate 62.5e6 --tx_rate > 62.5e6 --channels="0,1,2,3" > --args="mgmt_addr=192.168.1.74,addr=192.168.61.2,use_dpdk=1" > > [INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; > UHD_4.0.0.0-50-ge520e3ff > EAL: Detected 8 lcore(s) > EAL: Detected 1 NUMA nodes > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > EAL: No free hugepages reported in hugepages-1048576kB > EAL: Probing VFIO support... > EAL: VFIO support initialized > [ERROR] [DPDK] No available DPDK devices (ports) found! > EAL: FATAL: already called initialization. > EAL: already called initialization. > > > On Mon, Feb 1, 2021 at 7:44 PM Marcus D Leech <[email protected]> > wrote: > >> Unfortunately that’s one I can’t help with. I don’t have any DPDK capable >> machines at my disposal. >> >> I vaguely recall that you have to be root for DPDK to work. Perhaps >> that’s the issue? >> >> Sent from my iPhone >> >> On Feb 1, 2021, at 7:11 PM, Rob Kossler <[email protected]> wrote: >> >> >> I'm not convinced anything went wrong in the build of DPDK. The build >> didn't indicate any problems. But I wouldn't be surprised to find out that >> things aren't being installed where they are expected. >> >> In any case, I realized a mistake in my original post which accounts for >> the discrepancy in the location of the library file mentioned in the >> error. I had been fooling with the uhd.conf setting for "dkdk_driver" >> which I had changed on one system but not the other. >> >> And most recently, I accidentally commented out this setting completely >> and things seem to be better. The new error is the following. Not sure >> why I'm getting this error message. Suggestions welcome. >> >> EAL: Detected 8 lcore(s) >> EAL: Detected 1 NUMA nodes >> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket >> EAL: No free hugepages reported in hugepages-1048576kB >> EAL: Probing VFIO support... >> EAL: VFIO support initialized >> [ERROR] [DPDK] No available DPDK devices (ports) found! >> EAL: FATAL: already called initialization. >> EAL: already called initialization. >> >> >> On Mon, Feb 1, 2021 at 6:23 PM Marcus D. Leech via USRP-users < >> [email protected]> wrote: >> >>> On 02/01/2021 06:15 PM, Rob Kossler via USRP-users wrote: >>> >>> Hi, >>> I have 2 systems (each with host PC and N310) for which I'm having >>> similar issues in trying to get DPDK up and running. After going through >>> the UHD Manual DPDK instructions and DPDK app note, I am past the point at >>> which the "dpdk-devbind" seems to work fine, but I get the following error >>> when I run benchmark_rate. >>> >>> I am running Ubuntu 20.04.LTS and installed DPDK 18.11.11 by >>> downloading/building from source. I built UHD (latest 4.0) from source and >>> it seemed happy finding DPDK and building with DPDK support. It seems like >>> a compatibility issue, but I can't figure it out. Any suggestions? >>> Rob >>> >>> // *** this is the error on System 1 >>> EAL: /usr/local/lib/libdpdk.so: invalid ELF header >>> EAL: FATAL: Cannot init plugins >>> EAL: Cannot init plugins >>> >>> // this is the error on System 2 (nearly the same but different library) >>> EAL: >>> /usr/local/share/dpdk/x86_64-native-linuxapp-gcc/lib//librte_pmd_ark.a: >>> invalid ELF header >>> EAL: FATAL: Cannot init plugins >>> EAL: Cannot init plugins >>> >>> >>> This would seem to indicate that something very horrible went wrong in >>> the build or DPDK--creating ELF headers that aren't correct for the >>> type of hardware they're being used on. >>> >>> _______________________________________________ >>> USRP-users mailing list >>> [email protected] >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> >>
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
