From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 120] secondary fails failure without option '--legacy-mem'
Date: Thu, 06 Dec 2018 04:13:26 +0000 [thread overview]
Message-ID: <bug-120-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=120
Bug ID: 120
Summary: secondary fails failure without option '--legacy-mem'
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
Issue Description: Primary is run with option '--legacy-mem
--base-virtaddr=0x30000000000' in shared library mode. Secondary is started
without '--legacy-mem --base-virtaddr=0x30000000000'.
Workaround: run secondary with option '--legacy-mem'
Question: Does not primary and secondary share rte_configuration. If yes,
secondary will be knowning by default if primary is started with
'--legacy-mem'. Why is that we need to pass '--legacy-mem'?
Reason: Checked DPDK documentation and FAQ unable to find the dependency
stating both primary and secondary requires '--legacy-mem'. Document version
18.11.0
Logs For error:
# ./dpdk-procinfo -v --log-level=eal,8 --huge-unlink -d librte_pmd_tap.so
-- --host-id versionfetch -m
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: RTE Version: 'DPDK 18.05.0'
EAL: open shared lib librte_pmd_tap.so
EAL: Registered [vdev] bus.
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_3240_37f93f8beb0
EAL: request: bus_vdev_mp
EAL: msg: bus_vdev_mp
EAL: msg: bus_vdev_mp
EAL: Probing VFIO support...
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
EAL: VFIO modules not loaded, skipping VFIO support...
EAL: Ask a virtual area of 0x2e000 bytes
EAL: Virtual area found at 0x30000000000 (size = 0x2e000)
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x3000002e000 (size = 0x61000)
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x30000200000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x7f7908009000 (size = 0x61000)
EAL: TSC frequency is ~2194932 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: Master lcore 0 is ready (tid=806a980;cpuset=[0])
EAL: sendmsg: mp_malloc_request
EAL: msg: mp_malloc_response
error allocating rte services array
EAL: FATAL: rte_service_init() failed
EAL: rte_service_init() failed
PANIC in main():
Cannot init EAL
5: [./dpdk-procinfo() [0x401489]]
4: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f7907145f45]]
3: [./dpdk-procinfo(main+0x19d) [0x402b99]]
2:
[/home/test/Downloads/dpdk-18.05/x86_64-native-linuxapp-gcc/lib/librte_eal.so.7.1(__rte_panic+0xba)
[0x7f790771378b]]
1:
[/home/test/Downloads/dpdk-18.05/x86_64-native-linuxapp-gcc/lib/librte_eal.so.7.1(rte_dump_stack+0x1a)
[0x7f790771fd7a]]
Aborted
work around: run secondary with option '--legacy-mem ' we get successful run.
Logs: # # ./dpdk-procinfo -v --log-level=eal,8 --huge-unlink -d
librte_pmd_tap.so --legacy-mem -- --host-id versionfetch --stats | grep -v ":
0"
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: RTE Version: 'DPDK 18.05.0'
EAL: open shared lib librte_pmd_tap.so
EAL: Registered [vdev] bus.
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_3348_6651c4de8b4
EAL: request: bus_vdev_mp
EAL: msg: bus_vdev_mp
EAL: msg: bus_vdev_mp
EAL: Probing VFIO support...
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
EAL: VFIO modules not loaded, skipping VFIO support...
EAL: Ask a virtual area of 0x2e000 bytes
EAL: Virtual area found at 0x30000000000 (size = 0x2e000)
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x3000002e000 (size = 0x61000)
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x30000200000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x7f83780eb000 (size = 0x61000)
EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the
kernel.
EAL: This may cause issues with mapping memory into secondary processes
EAL: Analysing 128 files
EAL: TSC frequency is ~2194929 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: Master lcore 0 is ready (tid=7814c980;cpuset=[0])
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
######################## NIC statistics for port 0 ########################
RX-packets: 18 RX-errors: 0 RX-bytes: 3770
RX-nombuf: 0
TX-packets: 18 TX-errors: 0 TX-bytes: 3770
Stats reg 0 TX-packets: 18 TX-bytes: 3770
############################################################################
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-12-06 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 4:13 bugzilla [this message]
2018-12-06 14:36 ` [Bug 120] secondary fails failure without option '--legacy-mem' bugzilla
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-120-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.