From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Jeff Venable, Sr." <jeff@vectranetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] processor/core count issue
Date: Fri, 17 Jul 2015 10:18:53 +0200 [thread overview]
Message-ID: <2812981.NNf05kipb2@xps13> (raw)
In-Reply-To: <SN1PR08MB137618A37C4230E03D29A131A0980@SN1PR08MB1376.namprd08.prod.outlook.com>
2015-07-17 03:40, Jeff Venable, Sr.:
> In a VM Fusion environment configured with 2 processors with 1 core each I get the following:
>
> PANIC in rte_eal_init():
> Cannot init logs
> 4: [/lib/x86_64-linux-gnu/libc.so<http://libc.so/>.6(__libc_start_main+0xf5) [0x7f9fd3bdaec5]]
> 3: [/usr/lib/dpdk-2.0.0/librte_eal.so<http://librte_eal.so/>.1(rte_eal_init+0x123a) [0x7f9fd4f462fa]]
> 2: [/usr/lib/dpdk-2.0.0/librte_eal.so<http://librte_eal.so/>.1(__rte_panic+0xc3) [0x7f9fd4f449e8]]
> 1: [/usr/lib/dpdk-2.0.0/librte_eal.so<http://librte_eal.so/>.1(rte_dump_stack+0x16) [0x7f9fd4f4daa6]]
> Aborted (core dumped)
>
> rte_socket_id() was returning 0xFFFFFFFF here:
>
> (gdb) bt
> #0 0x00007ffff797ae95 in rte_malloc_socket () from /usr/lib/dpdk-2.0.0/librte_malloc.so.1
> #1 0x00007ffff797af4e in rte_zmalloc_socket () from /usr/lib/dpdk-2.0.0/librte_malloc.so.1
> #2 0x00007ffff7573ef8 in rte_ring_create () from /usr/lib/dpdk-2.0.0/librte_ring.so.1
> #3 0x00007ffff777770d in rte_mempool_xmem_create () from /usr/lib/dpdk-2.0.0/librte_mempool.so.1
> #4 0x00007ffff7777b97 in rte_mempool_create () from /usr/lib/dpdk-2.0.0/librte_mempool.so.1
> #5 0x00007ffff7b90899 in ?? () from /usr/lib/dpdk-2.0.0/librte_eal.so.1
> #6 0x00007ffff7b88d34 in ?? () from /usr/lib/dpdk-2.0.0/librte_eal.so.1
> #7 0x00007ffff7b84950 in rte_eal_init () from /usr/lib/dpdk-2.0.0/librte_eal.so.1
Please could you show which code is crashing and what is the root cause?
prev parent reply other threads:[~2015-07-17 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 3:40 Jeff Venable, Sr.
2015-07-17 8:18 ` Thomas Monjalon [this message]
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=2812981.NNf05kipb2@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jeff@vectranetworks.com \
/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).