From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 13] Cannot initialize Intel XL710 40G interface
Date: Wed, 31 Jan 2018 13:50:06 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path:
List-Id: DPDK patches and discussions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dev-bounces@dpdk.org
Sender: "dev"
https://dpdk.org/tracker/show_bug.cgi?id=3D13
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 N=
UMA
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 th=
is
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 t=
he
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?
--=20
You are receiving this mail because:
You are the assignee for the bug.=