From: Bing Zhao <bingz@nvidia.com>
To: Kevin Williams <kevin.williams@vastech.co.za>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: ibverbs_1.8 not found
Date: Wed, 24 Apr 2024 14:20:36 +0000 [thread overview]
Message-ID: <DM4PR12MB5184B55FC3DB6E4B6DD3787CD0102@DM4PR12MB5184.namprd12.prod.outlook.com> (raw)
In-Reply-To: <fca2699dd4c34605968d50330e288e3b@vastech.co.za>
Hi Kevin,
Usually, the issue is irrelevant to the FW but the building/linking and runtime ENV.
If possible, could you rebuild your DPDK libs and APP from the source code and the scratch on this running setup to have another try?
1. Please use "ls -al" of the ibverbs.so to check the actual version in the suffix.
2. Try to use "ldd" / "objdump/nm" to check the so version that the DPDK application linked and wants to load.
BR. Bing
> -----Original Message-----
> From: Kevin Williams <kevin.williams@vastech.co.za>
> Sent: Wednesday, April 24, 2024 9:56 PM
> To: users@dpdk.org
> Subject: ibverbs_1.8 not found
>
> External email: Use caution opening links or attachments
>
>
> Hi,
>
> I have just installed a fresh Rocky 8.8 on a server with two Mellanox interfaces,
> which seem to have the correct firmware according to Nvidia:
>
> Device Type: ConnectX3
> Part Number: MCX353A-FCB_A2-A5
> Description: ConnectX-3 VPI adapter card; single-port QSFP; FDR IB
> (56Gb/s) and 40GigE; PCIe3.0 x8 8GT/s; RoHS R6
> PCI Device Name: /dev/mst/mt4099_pci_cr1
> Versions: Current Available
> FW 2.42.5000 N/A
> PXE 3.4.0752 N/A
>
> Status: No matching image found
>
> I have followed all instructions on the Ettus web page
> (https://kb.ettus.com/Getting_Started_with_DPDK_and_UHD) which
> proceeded without any issues.
>
> When running an Ettus benchmark utility I get the following error.
>
> [root@rflab-r720 python]# ./benchmark_rate.py --rx_rate 184.32e6 --
> rx_subdev "A:0 B:0" --rx_channels "0" --tx_rate 184.32e6 --tx_subdev "A:0
> B:0" --tx_channels 0 --args
> "addr=10.28.128.3,second_addr=10.29.128.3,master_clock_rate=184.32e6,
> use_dpdk=1"
> [INFO] [UHD] linux; GNU C++ version 8.5.0 20210514 (Red Hat 8.5.0-20);
> Boost_106600; DPDK_21.11; UHD_
> EAL: Detected CPU lcores: 24
> EAL: Detected NUMA nodes: 2
> EAL: Detected shared linkage of DPDK
> EAL: /usr/lib64/libibverbs.so.1: version `IBVERBS_1.8' not found (required by
> /usr/lib64/dpdk-pmds/librte_common_mlx5.so.22.0)
> EAL: FATAL: Cannot init plugins
> EAL: Cannot init plugins
> [ERROR] [DPDK] Error with EAL initialization [ERROR] [UHD] Device discovery
> error: RuntimeError: Error with EAL initialization
> EAL: Detected CPU lcores: 24
> EAL: Detected NUMA nodes: 2
> EAL: Option -l is ignored, because (-l) is set!
>
> I see there are two locations for libibverbs.so.1, but setting LD_LIBRARY_PATH
> to either results in the same error.
>
> /usr/lib64/mlnx_ofed/valgrind/libibverbs.so.1
> /usr/lib64/libibverbs.so.1
>
> I can't install a new libibverbs RPM because of obsolescence issues.
>
> Can anyone offer any advice?
>
> Many thanks, Kevin
>
prev parent reply other threads:[~2024-04-24 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 13:55 Kevin Williams
2024-04-24 14:20 ` Bing Zhao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM4PR12MB5184B55FC3DB6E4B6DD3787CD0102@DM4PR12MB5184.namprd12.prod.outlook.com \
--to=bingz@nvidia.com \
--cc=kevin.williams@vastech.co.za \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).