From: Cliff Burdick <shaklee3@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] WARNING! Base virtual address hint not respected!
Date: Thu, 15 Nov 2018 11:30:06 -0800 [thread overview]
Message-ID: <CA+Gp1nbBD+or88Oh+oS20FM4hG-nLfPqWzoMTfpiuCML2g_8Kg@mail.gmail.com> (raw)
Hi, I'm updating to 18.11 from 17.03, and I noticed there a several new
warnings printing on startup in my primary process:
EAL: Detected 48 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: WARNING! Base virtual address hint (0x64002f000 != 0x680000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0xe80030000 != 0xec0000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x16c0031000 != 0x1700000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x1f00032000 != 0x1f40000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x2740033000 != 0x2780000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x2f80034000 != 0x2fc0000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x37c0035000 != 0x3800000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING! Base virtual address hint (0x4000036000 != 0x4040000000) not
respected!
EAL: This may cause issues with mapping memory into secondary processes
It appears by searching the mailing list that this problem is not very
common since it's fairly new. Does anyone know what can cause this? I have
ASLR disabled.
next reply other threads:[~2018-11-15 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 19:30 Cliff Burdick [this message]
2018-11-15 19:54 ` Kyle Larose
2018-11-15 20:33 ` Cliff Burdick
2018-11-17 3:51 ` Cliff Burdick
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=CA+Gp1nbBD+or88Oh+oS20FM4hG-nLfPqWzoMTfpiuCML2g_8Kg@mail.gmail.com \
--to=shaklee3@gmail.com \
--cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).