From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Kenvish Butani <kenvishwlan@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] testpmd crashes with Invalid NUMA socket, default to 0
Date: Mon, 22 Oct 2018 10:15:08 +0100 [thread overview]
Message-ID: <0db47ae8-8811-0a21-b56e-ac8d58f403cc@intel.com> (raw)
In-Reply-To: <CAL4cODNrEV68Uq-caHX0KeV2jYqek0ouCFfwGnBQi7QuLmHQUA@mail.gmail.com>
On 22-Oct-18 7:34 AM, Kenvish Butani wrote:
> Hi All,
>
> I am new to dpdk, and trying it to integrate DPDK with one of my server
> having intel nic's and 24 core cpu.
>
> I am trying to run testpmd app and it gets crashed with below logs
>
> ++++++++++++++++++++++++++++++++++++++
> # ./testpmd-cc-on-local -c 0xF -n 1 -w 01:00.0 -- -i
> EAL: Detected 24 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Probing VFIO support...
> EAL: PCI device igb_uio 0000:01:00.0: uio device registered with irq 44
> 0000:01:00.0 on NUMA socket -1
> EAL: Invalid NUMA socket, default to 0
> EAL: probe driver: 8086:10a7 net_e1000_igb
> EAL: Error - exiting with code: 1
> Cause: rte_zmalloc(32 struct rte_port) failed
> ++++++++++++++++++++++++++++++++++++++
Hi Kenvish,
The error looks like you don't have any memory available. Adding
--log-level=eal,8 will reveal more info on what is happening during
attempt at allocation time.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-10-22 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 6:34 Kenvish Butani
2018-10-22 9:15 ` Burakov, Anatoly [this message]
2018-10-22 9:28 ` Kenvish Butani
2018-10-22 9:46 ` Burakov, Anatoly
2018-10-22 11:08 ` Kenvish Butani
2018-10-22 11:19 ` Burakov, Anatoly
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=0db47ae8-8811-0a21-b56e-ac8d58f403cc@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kenvishwlan@gmail.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).