From: Thomas DETHIER <t.dethier@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Can not initialize Intel XX710-DA2 on Ubuntu 22.04
Date: Fri, 13 May 2022 10:45:08 +0000 [thread overview]
Message-ID: <6fb7079f2c734816a961f4fce506ddb8@deltacast.tv> (raw)
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
Hello,
I have been having some issues trying to make an Intel XXV710-DA2 on Ubuntu Server 22.04 working using either DPDK 21.10 and 22.03.
When I run the following command :
sudo ./dpdk-testpmd -l 1-7 -n 4 -a 65:00.0,txqs_min_inline=1,tx_pp=500 -- --socket-num=0 --burst=10 --txd=1024 --rxd=1024 --mbcache=512 --rxq=1 --txq=1 --nb-cores=1 --txpkts=1500 -i --txonly-multi-flow --forward-mode=txonly --eth-peer=0,01:00:5e:00:00:08 --tx-ip=10.10.1.168,239.0.0.8
I get that output :
EAL: Detected CPU lcores: 8
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
EAL: Probe PCI driver: net_i40e (8086:158b) device: 0000:65:00.0 (socket 0)
eth_i40e_dev_init(): Failed to init adminq: -66
ethdev initialisation failed
EAL: Requested device 0000:65:00.0 cannot be used
EAL: Bus (pci) probe failed.
TELEMETRY: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Fail: input rxq (1) can't be greater than max_rx_queues (0) of port 0
EAL: Error - exiting with code: 1
Cause: rxq 1 invalid - must be >= 0 && <= 0
It seems that DPDK can't initialize the Nic. Did anybody already tested this particular Nic with Ubuntu Server 22.04 ? Was it successful ?
Thanks in advance,
Thomas DETHIER | Test Project Engineer | DELTATEC
t.dethier@deltacast.tv<mailto:t.dethier@deltacast.tv>
www.deltacast.tv<http://www.deltacast.tv>
[-- Attachment #2: Type: text/html, Size: 6929 bytes --]
reply other threads:[~2022-05-13 10:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6fb7079f2c734816a961f4fce506ddb8@deltacast.tv \
--to=t.dethier@deltacast.tv \
--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).