From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 13] Cannot initialize Intel XL710 40G interface
Date: Wed, 31 Jan 2018 13:50:06 +0000 [thread overview]
Message-ID: <bug-13-3@http.dpdk.org/tracker/> (raw)
https://dpdk.org/tracker/show_bug.cgi?id=13
Bug ID: 13
Summary: Cannot initialize Intel XL710 40G interface
Product: DPDK
Version: 17.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: gabor.sandor.enyedi@ericsson.com
Target Milestone: ---
We have an AMD Threadripper 1950X, w/ 2 NUMA nodes. I cannot initialize our
XL710 cards in the slots belonging to NUMA node #0. In slots belonging to NUMA
node #1 it seems to be OK. I get this at initialization:
EAL: Detected 32 lcore(s)
EAL: Debug dataplane logs available - lower performance
EAL: Probing VFIO support...
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
eth_i40e_dev_init(): Failed to init adminq: -54
EAL: Requested device 0000:09:00.0 cannot be used
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
eth_i40e_dev_init(): Failed to init adminq: -54
EAL: Requested device 0000:09:00.1 cannot be used
EAL: PCI device 0000:41:00.0 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:41:00.1 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
I.e. the 2 ports in the card belonging to NUMA #1 was initialized correctly
(41:00.x), but the other two fails.
This machine can "hide" its NUMA behavior by setting so in BIOS (i.e. in this
case I see one single NUMA node w/ 16 cores), but this feature does not help
eiter. I get the same both when have 1 or 2 XL710 cards in the box. I get the
same with the latest DPDK from git. Using the kernel, everything seems to be
OK.
What tests can I do to help finding the bug?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-01-31 13:50 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-13-3@http.dpdk.org/tracker/ \
--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 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).