From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 498] can not start testpmd after use meson/ninja build 32-bit app on x86 system
Date: Wed, 01 Jul 2020 01:38:12 +0000 [thread overview]
Message-ID: <bug-498-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=498
Bug ID: 498
Summary: can not start testpmd after use meson/ninja build
32-bit app on x86 system
Product: DPDK
Version: 20.05
Hardware: x86
OS: Linux
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
$cd dpdk
$./devtools/test-meson-builds.sh
2. start testpmd
$./build-x86-default/app/dpdk-testpmd -c 0xf -n 4 -- -i
3. the output of testpmd
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: Cannot get a virtual area of any size: Success
EAL: Cannot allocate VA space for memseg list, retrying with different page
size
EAL: Cannot allocate VA space on socket 0
EAL: FATAL: Cannot init memory
EAL: Cannot init memory
EAL: Error - exiting with code: 1
Cause: Cannot init EAL: Cannot allocate memory
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-07-01 1:38 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-498-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.