From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1020] Can not detect E810-CQDA2 on Ubuntu 20.04
Date: Mon, 30 May 2022 10:41:16 +0000 [thread overview]
Message-ID: <bug-1020-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1020
Bug ID: 1020
Summary: Can not detect E810-CQDA2 on Ubuntu 20.04
Product: DPDK
Version: 22.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: t.dethier@deltacast.tv
Target Milestone: ---
I have been experiencing issues with an Intel E810-CQDA2 and Ubuntu Server
20.04 on DPDK 21.10 and 22.03 :
Command used :
sudo ./dpdk-testpmd -l 1-7 -n 4 -a 17:00.0 -- --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 --tx-ip=10.10.1.168,239.0.0.8
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
>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 seem that the Nic isn’t detected by DPDK when running the tests, but when I
run dpdk-devbind
$ dpdk-devbind.py -s
>Network devices using DPDK-compatible driver
>============================================
>0000:17:00.0 'Ethernet Controller E810-C for QSFP 1592' drv=igb_uio
>>unused=ice,vfio-pci
I don’t understand why I can’t use the device although it is binded to DPDK.
I've tested with DPDK 20.11.3 and everything is working fine, the Nic is
detected.
More information abotu my setup :
OS : Ubuntu Server 20.04
Kernerl : 5.4.0-113-generic
ICE version : 1.8.8
firmware-version: 3.20 0x8000d83e 0.0.0
Motherboard : SuperMicro X11SRM-F
CPU : 8 CPUs x Intel Xeon W-2245 @ 3.90GHz
Memory : 64GB DDR4
>$ modinfo ice
>filename:
>/lib/modules/5.4.0-113-generic/updates/drivers/net/ethernet/intel/ice/ice.ko
>firmware: updates/intel/ice/ddp/ice.pkg
>version: 1.8.8
>license: GPL v2
>description: Intel(R) Ethernet Connection E800 Series Linux Driver
>author: Intel Corporation, <linux.nics@intel.com>
>srcversion: C37D0CEC677B3E87490CA38
>alias: pci:v00008086d00001888sv*sd*bc*sc*i*
>alias: pci:v00008086d0000151Dsv*sd*bc*sc*i*
>alias: pci:v00008086d0000124Fsv*sd*bc*sc*i*
>alias: pci:v00008086d0000124Esv*sd*bc*sc*i*
>alias: pci:v00008086d0000124Dsv*sd*bc*sc*i*
>alias: pci:v00008086d0000124Csv*sd*bc*sc*i*
>alias: pci:v00008086d0000189Asv*sd*bc*sc*i*
>alias: pci:v00008086d00001899sv*sd*bc*sc*i*
>alias: pci:v00008086d00001898sv*sd*bc*sc*i*
>alias: pci:v00008086d00001897sv*sd*bc*sc*i*
>alias: pci:v00008086d00001894sv*sd*bc*sc*i*
>alias: pci:v00008086d00001893sv*sd*bc*sc*i*
>alias: pci:v00008086d00001892sv*sd*bc*sc*i*
>alias: pci:v00008086d00001891sv*sd*bc*sc*i*
>alias: pci:v00008086d00001890sv*sd*bc*sc*i*
>alias: pci:v00008086d0000188Esv*sd*bc*sc*i*
>alias: pci:v00008086d0000188Dsv*sd*bc*sc*i*
>alias: pci:v00008086d0000188Csv*sd*bc*sc*i*
>alias: pci:v00008086d0000188Bsv*sd*bc*sc*i*
>alias: pci:v00008086d0000188Asv*sd*bc*sc*i*
>alias: pci:v00008086d0000159Bsv*sd*bc*sc*i*
>alias: pci:v00008086d0000159Asv*sd*bc*sc*i*
>alias: pci:v00008086d00001599sv*sd*bc*sc*i*
>alias: pci:v00008086d00001593sv*sd*bc*sc*i*
>alias: pci:v00008086d00001592sv*sd*bc*sc*i*
>alias: pci:v00008086d00001591sv*sd*bc*sc*i*
>depends: auxiliary
>retpoline: Y
>name: ice
>vermagic: 5.4.0-113-generic SMP mod_unload modversions
>parm: debug:netif level (0=none,...,16=all) (int)
>parm: fwlog_level:FW event level to log. All levels <= to the
>specified value are enabled. Values: 0=none, 1=error, 2=warning, 3=normal,
>4=verbose. Invalid values: >=5
> (ushort)
>parm: fwlog_events:FW events to log (32-bit mask)
> (ulong)
>$ ethtool -i enp23s0f1
>driver: ice
>version: 0.8.1-k
>firmware-version: 3.20 0x8000d83e 0.0.0
>expansion-rom-version:
>bus-info: 0000:17:00.1
>supports-statistics: yes
>supports-test: yes
>supports-eeprom-access: yes
>supports-register-dump: yes
>supports-priv-flags: yes
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-05-30 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 10:41 bugzilla [this message]
2022-06-07 9:26 ` bugzilla
2022-06-07 9:27 ` bugzilla
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=bug-1020-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).