From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 59] Cannot start secondary processes anyhow on
	Redhat EL7
Date: Fri, 01 Jun 2018 16:05:42 +0000
Message-ID: <bug-59-3@http.dpdk.org/tracker/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://dpdk.org/tracker/show_bug.cgi?id=3D59

            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.lanzuisi@resi.it
  Target Milestone: ---

Created attachment 7
  --> https://dpdk.org/tracker/attachment.cgi?id=3D7&action=3Dedit
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=3DX" where X is the val=
ue
returned by the tiny process;
- the secondary process started and attached to the rings and mempools crea=
ted
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=20

"WARNING! Base virtual address hint (0x7fff80000000 !=3D 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 memor=
y 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.

--=20
You are receiving this mail because:
You are the assignee for the bug.=