From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 499] failed to start example after use meson/ninja build 32-bit app on x86 system
Date: Fri, 03 Jul 2020 08:24:53 +0000 [thread overview]
Message-ID: <bug-499-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=499
Bug ID: 499
Summary: failed to start example after use meson/ninja build
32-bit app on x86 system
Product: DPDK
Version: 20.05
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: lihongx.ma@intel.com
Target Milestone: ---
os:
ubuntu18.04 4.15.0-101-generic x86_64 GNU/Linux
step:
1. build the dpdk
$find /usr -type d -name pkgconfig
/usr/share/pkgconfig
/usr/lib/i386-linux-gnu/pkgconfig
/usr/lib/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/local/lib/x86_64-linux-gnu/pkgconfig
$export PKG_CONFIG_LIBDIR=/usr/lib/i386-linux-gnu/pkgconfig/
$export CFLAGS=-m32
2. start the example
$cd dpdk
$./devtools/test-meson-builds.sh
./build-x86-default/examples/dpdk-l3fwd -v -c 0x40000000 -n 4 -- -p 0x3
--config '(0,0,30),(1,0,30),(0,1,30),(1,1,30)'
3. the output of app
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: RTE Version: 'DPDK 20.05.0-rc3'
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No free hugepages reported in hugepages-2048kB
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Cannot allocate VA space on socket 1
EAL: FATAL: Cannot init memory
EAL: Cannot init memory
EAL: Error - exiting with code: 1
Cause: Invalid EAL parameters
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-07-03 8:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-499-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.