From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1445] [dpdk-24.07] dpdk-test-dma-perf hang on Ubuntu24.04
Date: Mon, 20 May 2024 09:01:23 +0000 [thread overview]
Message-ID: <bug-1445-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3117 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1445
Bug ID: 1445
Summary: [dpdk-24.07] dpdk-test-dma-perf hang on Ubuntu24.04
Product: DPDK
Version: 24.07
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
[Environment]
DPDK version: 24.07.0-rc0
OS: Ubuntu 24.04 LTS (Noble Numbat); 6.8.0-31-generic
Compiler: gcc version 13.2.0
Hardware platform: Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz
NIC hardware & NIC firmware:
root@dut245:~/dpdk# ethtool -i ens801f0np0
driver: ice
version: 6.8.0-31-generic
firmware-version: 4.30 0x80019938 1.3403.0
[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.
1.Bind 2 CBDMA to vfio-pci driver:
./usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:00:04.0 0000:00:04.1
2.Create test_config.ini
/root/dpdk/test_default_config.ini
root@dut220:~/dpdk# cat /root/dpdk/test_default_config.ini
[case1]
type = DMA_MEM_COPY
mem_size = 10
buf_size = 64,8192,2,MUL
dma_ring_size = 1024
kick_batch = 32
src_numa_node = 0
dst_numa_node = 0
cache_flush = 0
test_seconds = 2
lcore_dma = lcore1@0000:00:04.0,lcore2@0000:00:04.1
eal_args = --in-memory --file-prefix=test
[case2]
type = CPU_MEM_COPY
mem_size = 10
buf_size = 64,8192,2,MUL
src_numa_node = 0
dst_numa_node = 0
cache_flush = 0
test_seconds = 2
lcore = 1,2
eal_args = --in-memory --no-pci
3, launch dma-perf testing
x86_64-native-linuxapp-gcc/app/dpdk-test-dma-perf --config
/root/dpdk/test_default_config.ini --result /root/dpdk/test_default_config.csv
root@dut220:~/dpdk# x86_64-native-linuxapp-gcc/app/dpdk-test-dma-perf --config
/root/dpdk/test_default_config.ini
config file parsing...
Transfer direction not configured. Defaulting it to MEM to MEM transfer.
config file parsing complete.
Running cases...
Running case 1
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Selected IOVA mode 'VA'
EAL: No free 2048 kB hugepages reported on node 0
EAL: No free 2048 kB hugepages reported on node 1
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:2021) device: 0000:00:04.0 (socket 0)
IOAT: ioat_dmadev_probe(): Init 0000:00:04.0 on NUMA node 0
EAL: Ignore mapping IO port bar(1)
EAL: Probe PCI driver: dmadev_ioat (8086:2021) device: 0000:00:04.1 (socket 0)
IOAT: ioat_dmadev_probe(): Init 0000:00:04.1 on NUMA node 0
Number of used lcores: 44.
Running scenario 1
Number of used dmadevs: 2.
Start testing....
[Actual Result]
dpdk-test-dma-perf hang
[Expected Result]
Test OK
[Regression]
Is this issue a regression: (N)
The first time to test on Ubuntu 24.04.
Notes: test passed on Ubuntu22.04.3
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5024 bytes --]
next reply other threads:[~2024-05-20 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 9:01 bugzilla [this message]
2024-05-23 10:01 ` [DPDK/other Bug 1445] [dpdk-24.07] dpdk-test-dma-perf hang on Ubuntu24.04 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-1445-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.