From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Qiu, Michael" <michael.qiu@intel.com>
Subject: Re: Getting error while running DPDK test app on X-Gene1
Date: Thu, 14 Jan 2016 08:26:19 +0000
Message-ID: <533710CFB86FA344BFBF2D6802E6028622F1870F@SHSMSX101.ccr.corp.intel.com>
References: <CAJC5FUX9m0g2aA3Tsh91OAeBkur89EGMKyVh6wyWbrhn32eDqg@mail.gmail.com>
 <20160114041503.GA2450@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jitendra Kanitkar <jkanitkar@apm.com>,
 Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, Ankit Jindal
 <ajindal@apm.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 1E9EA5954
 for <dev@dpdk.org>; Thu, 14 Jan 2016 09:26:24 +0100 (CET)
Content-Language: en-US
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 1/14/2016 12:15 PM, Jerin Jacob wrote:=0A=
> On Wed, Jan 13, 2016 at 03:52:01PM +0530, Ankit Jindal wrote:=0A=
>> Hi,=0A=
>>=0A=
>> We are trying to run dpdk on our arm64 based SOC having Intel 10G=0A=
>> ixgbe PCIe card plugged. While running any test app, we are getting=0A=
>> following error.=0A=
>>=0A=
>> EAL: PCI device 0000:01:00.0 on NUMA socket 0=0A=
>> EAL:   probe driver: 8086:10fb rte_ixgbe_pmd=0A=
>> EAL: Cannot open /sys/bus/pci/devices/0000:01:00.0/resource0: No such=0A=
>> file or directory=0A=
>> EAL: Error - exiting with code: 1=0A=
>>   Cause: Requested device 0000:01:00.0 cannot be used=0A=
>=0A=
> pci resource creation patch is not yet part of the arm64 mainline kernel.=
=0A=
> The following patch should fix the problem.=0A=
>=0A=
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/358906.ht=
ml=0A=
>=0A=
> Jerin=0A=
=0A=
What's the status of your arm kernel patch?=0A=
=0A=
Thanks,=0A=
Michael=0A=
>> Below are the details on modules, hugepages and device binding.=0A=
>> root@arm64:~# lsmod=0A=
>> Module                  Size  Used by=0A=
>> rte_kni               292795  0=0A=
>> igb_uio                 4338  0=0A=
>> ixgbe                 184456  0=0A=
>>=0A=
>> root@arm64:~/dpdk# cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_huge=
pages=0A=
>> 2048=0A=
>>=0A=
>> root@arm64:~/dpdk# ./tools/dpdk_nic_bind.py --status=0A=
>>=0A=
>> Network devices using DPDK-compatible driver=0A=
>> =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=0A=
>> 0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection'=0A=
>> drv=3Digb_uio unused=3D=0A=
>> 0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection'=0A=
>> drv=3Digb_uio unused=3D=0A=
>>=0A=
>> Network devices using kernel driver=0A=
>> =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=0A=
>> <none>=0A=
>>=0A=
>> Other network devices=0A=
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
>> <none>=0A=
>> root@arm64:~/dpdk#=0A=
>>=0A=
>> Thanks,=0A=
>> Ankit=0A=
=0A=