From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1269] test-dma-perf running in iova-mode as PA for rte_memcpy results in seg-fault.
Date: Thu, 27 Jul 2023 14:28:39 +0000 [thread overview]
Message-ID: <bug-1269-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3743 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1269
Bug ID: 1269
Summary: test-dma-perf running in iova-mode as PA for
rte_memcpy results in seg-fault.
Product: DPDK
Version: 23.07
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: vipin.varghese@amd.com
Target Milestone: ---
Platform:
CPU: AMD EPYC 9374F 32-Core Processor
OS: RHEL 8.5
Kernel: 4.18.0-372.26.1.el8_6.x86_64
DPDK Application: dpdk-test-dma-perf
Configuration:
```
[case1]
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 = 7
eal_args=--in-memory --no-pci
```
Logs:
```
EAL: Virtual area found at 0x1180000000 (size = 0x61000)
EAL: Memseg list allocated at socket 0, page size 0x800kB
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x1180200000 (size = 0x400000000)
EAL: VA reserved for memseg list at 0x1180200000, size 400000000
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x1580200000 (size = 0x61000)
EAL: Memseg list allocated at socket 0, page size 0x800kB
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x1580400000 (size = 0x400000000)
EAL: VA reserved for memseg list at 0x1580400000, size 400000000
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x1980400000 (size = 0x61000)
EAL: Memseg list allocated at socket 0, page size 0x800kB
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x1980600000 (size = 0x400000000)
EAL: VA reserved for memseg list at 0x1980600000, size 400000000
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x1d80600000 (size = 0x61000)
EAL: Memseg list allocated at socket 0, page size 0x800kB
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x1d80800000 (size = 0x400000000)
EAL: VA reserved for memseg list at 0x1d80800000, size 400000000
EAL: Using memfd for anonymous memory
EAL: No shared files mode enabled, IPC is disabled
EAL: No shared files mode enabled, IPC is disabled
EAL: TSC frequency is ~3840000 KHz
EAL: Main lcore 1 is ready (tid=7ff91da0cc00;cpuset=[1])
EAL: lcore 2 is ready (tid=7ff91be46400;cpuset=[2])
EAL: lcore 3 is ready (tid=7ff91b645400;cpuset=[3])
EAL: lcore 4 is ready (tid=7ff91ae44400;cpuset=[4])
EAL: lcore 7 is ready (tid=7ff919641400;cpuset=[7])
EAL: lcore 6 is ready (tid=7ff919e42400;cpuset=[6])
EAL: lcore 5 is ready (tid=7ff91a643400;cpuset=[5])
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: alloc_seg(): mmap() failed: Cannot allocate memory
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x1180200000 (size = 0x200000)
EAL: attempted to allocate 1 segments, but only 0 were allocated
EAL: Restoring previous memory policy: 0
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: No shared files mode enabled, IPC is disabled
EAL: Heap on socket 0 was expanded by 1024MB
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
EAL: lib.telemetry log level changed from disabled to warning
TELEMETRY: No legacy callbacks, legacy socket not created
Number of used lcores: 7.
Running scenario 1
Start testing....
Case process killed by signal 11
Bye...
```
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5627 bytes --]
next reply other threads:[~2023-07-27 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:28 bugzilla [this message]
2023-11-28 16:25 ` [Bug 1269] test-dma-perf running in iova-mode as PA for rte_memcpy results in seg-fault 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-1269-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.