https://dpdk.org/tracker/show_bug.cgi?id=59
Bug ID: 59
Summary: Cannot start secondary processes anyhow on Redhat EL7
Product: DPDK
Version: 18.02
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: major
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: m.lanzu...@resi.it
Target Milestone: ---
Created attachment 7
--> https://dpdk.org/tracker/attachment.cgi?id=7&action=edit
Core Dump GDB Output
Hi all,
I was using DPDK 2.2.0 on Redhat EL6. It worked with this configuration:
- a tiny process launched the "rte_eal_get_physmem_layout()" function;
- the primary process started with "--base-virtaddr=X" where X is the value
returned by the tiny process;
- the secondary process started and attached to the rings and mempools created
by the primary process.
Now I downloaded dpdk-18.02.1.tar.xz, recompiled all the processes with the new
version, changed some functions for compatibility and ran everything on a
Redhat EL7.
ASLR is disabled, but I had the
"WARNING! Base virtual address hint (0x7fff80000000 != 0x7ffefffcd000) not
respected!"
messages when starting the primary process, so changed manually the
"--base-virtaddr" parameter to avoid these warnings.
After the warnings did not happen any more, when starting the secondary
process, it fails with a segfault.
To avoid the warnings, I set the address "0x7ffa3ffcd000"
Inside the core dump attached you can see that address requested by the
secondary process is "0x7ffabfd47080" and the gdb says "Cannot access memory at
address 0x7ffabfd47080.
The function that generates the error is "rte_ctrlmbuf_alloc()".
I don't know if any other parameter in the kernel/hugepages spaces must be set.
--
You are receiving this mail because:
You are the assignee for the bug.
