From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <prashant.upadhyaya@aricent.com>
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11])
 by dpdk.org (Postfix) with ESMTP id 6D47368E8
 for <dev@dpdk.org>; Fri, 14 Feb 2014 09:30:45 +0100 (CET)
Received: from jaguar.aricent.com (localhost [127.0.0.1])
 by postfix.imss71 (Postfix) with ESMTP id CC48836B8C
 for <dev@dpdk.org>; Fri, 14 Feb 2014 14:01:48 +0530 (IST)
Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com
 [10.203.171.136]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
 (No client certificate requested)
 by jaguar.aricent.com (Postfix) with ESMTP id B514A36B7B
 for <dev@dpdk.org>; Fri, 14 Feb 2014 14:01:48 +0530 (IST)
Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by
 GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.136]) with mapi; Fri, 14 Feb 2014
 14:01:48 +0530
From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Date: Fri, 14 Feb 2014 14:01:27 +0530
Thread-Topic: DPDK not recognizing 82599 on my setup
Thread-Index: Ac8pWn0C//P+BH8vT4KkdEOYeQW5nwABJvDg
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C5A2A3635C2@GUREXMB01.ASIAN.AD.ARICENT.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-TM-AS-MML: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] DPDK not recognizing 82599 on my setup
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 08:30:46 -0000

Hi,

Here is the lscpi output -

81:00.0 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit SF=
I/SFP+ Network Connection [8086:10fb] (rev 01)
81:00.1 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit SF=
I/SFP+ Network Connection [8086:10fb] (rev 01)
84:00.0 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit SF=
I/SFP+ Network Connection [8086:10fb] (rev 01)
84:00.1 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit SF=
I/SFP+ Network Connection [8086:10fb] (rev 01)

I am using Fedora 18, DPDK version 1.5.0r1

The first two ports (as in lspci output) are connected to the switch and Li=
nux is able to ping using these.
When they are in linux control, I see that auto negotiation is done for 10 =
Gbps
I unbind 81:00.0 and apply igb_uio

Now when I start the DPDK application, I get the error which I am attaching=
 with DEBUG set to y.
Somehow DPDK is not able to recognize the NIC.

Any hints if someone has encountered a similar issue.

Regards
-Prashant





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D