From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bugzilla@dpdk.org>
Received: by dpdk.org (Postfix, from userid 33)
 id 951481B7C7; Wed, 31 Jan 2018 14:50:06 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Wed, 31 Jan 2018 13:50:06 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: ethdev
X-Bugzilla-Version: 17.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gabor.sandor.enyedi@ericsson.com
X-Bugzilla-Status: CONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-13-3@http.dpdk.org/tracker/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://dpdk.org/tracker/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 13] Cannot initialize Intel XL710 40G interface
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2018 13:50:06 -0000

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.=