From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1387] [dpdk24.03] cbdma: Failed to launch dpdk-dma app
Date: Wed, 28 Feb 2024 03:22:17 +0000 [thread overview]
Message-ID: <bug-1387-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3645 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1387
Bug ID: 1387
Summary: [dpdk24.03] cbdma: Failed to launch dpdk-dma app
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
[Environment]
DPDK version:
92c0ad70ca (HEAD -> main, tag: v24.03-rc1, origin/main, origin/HEAD) version:
24.03-rc1
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 22.04.3 LTS/5.15.0-92-generic
Compiler: gcc version 11.4.0
Hardware platform: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
NIC hardware: Ethernet Controller E810-C for QSFP 1592
NIC firmware:
driver: ice
version: 1.13.7
firmware-version: 4.40 0x8001c967 1.3534.0
[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.
1, Build app
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc -j 100 meson configure -Dexamples=dma
x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
ls x86_64-native-linuxapp-gcc/examples/dpdk-dma
2, Bind nic and dma to vfio-pci
./usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:4b:00.0 0000:00:01.0
3, Launch app
x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 5-6 -n 8 -a 0000:4b:00.0 -a
0000:00:01.0 --file-prefix=cbdma_690149_20240219131328
--proc-type=primary -- -p 0x1 -q 1 --mac-updating -c hw
Show the output from the previous commands:
x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 5-6 -n 8 -a 0000:4b:00.0 -a
0000:00:01.0 --file-prefix=cbdma_690149_20240219131328
--proc-type=primary -- -p 0x1 -q 1 --mac-updating -c hw
Exception happened in [x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 5-6 -n
8 -a 0000:4b:00.0 -a 0000:00:01.0 --file-prefix=cbdma_690149_20240219131328
--proc-type=primary -- -p 0x1 -q 1 --mac-updating -c hw] and output is [EAL:
Detected CPU lcores: 80
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/cbdma_690149_20240219131328/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 4096 hugepages of size 2097152 reserved, but no mounted hugetlbfs found
for that size
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(1)
EAL: Probe PCI driver: dmadev_ioat (8086:0b00) device: 0000:00:01.0 (socket 0)
IOAT: ioat_dmadev_probe(): Init 0000:00:01.0 on NUMA node 0
EAL: Ignore mapping IO port bar(1)
EAL: Ignore mapping IO port bar(4)
EAL: Probe PCI driver: net_ice (8086:1592) device: 0000:4b:00.0 (socket 0)
ice_load_pkg_type(): Active package is: 1.3.36.0, ICE OS Default Package
(double VLAN mode)
Invalid max frame size, 0.
EAL: Error - exiting with code: 1
Cause: Invalid DMA arguments
IOAT: ioat_dmadev_remove(): Closing 0000:00:01.0 on NUMA node 0]
[Expected Result]
Launch app successfully
[Regression]
Is this issue a regression: (Y/N) Y
Version the regression was introduced:
commit 8d85afb19af706de662e7ee686e6e437f835c6e3
Author: Chengwen Feng <fengchengwen@huawei.com>
Date: Fri Jan 26 06:10:13 2024 +0000
examples/dma: replace getopt with argparse
Replace getopt with argparse.
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5646 bytes --]
next reply other threads:[~2024-02-28 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 3:22 bugzilla [this message]
2024-03-08 2:32 ` [DPDK/examples Bug 1387] [dpdk24.03] cbdma: Failed to launch dpdk-dma app 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-1387-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.