From: "Qiu, Michael" <michael.qiu@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Ankit Jindal <ajindal@apm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jitendra Kanitkar <jkanitkar@apm.com>,
Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
Subject: Re: [dpdk-dev] Getting error while running DPDK test app on X-Gene1
Date: Thu, 14 Jan 2016 08:26:19 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028622F1870F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20160114041503.GA2450@localhost.localdomain>
On 1/14/2016 12:15 PM, Jerin Jacob wrote:
> On Wed, Jan 13, 2016 at 03:52:01PM +0530, Ankit Jindal wrote:
>> Hi,
>>
>> We are trying to run dpdk on our arm64 based SOC having Intel 10G
>> ixgbe PCIe card plugged. While running any test app, we are getting
>> following error.
>>
>> EAL: PCI device 0000:01:00.0 on NUMA socket 0
>> EAL: probe driver: 8086:10fb rte_ixgbe_pmd
>> EAL: Cannot open /sys/bus/pci/devices/0000:01:00.0/resource0: No such
>> file or directory
>> EAL: Error - exiting with code: 1
>> Cause: Requested device 0000:01:00.0 cannot be used
>
> pci resource creation patch is not yet part of the arm64 mainline kernel.
> The following patch should fix the problem.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/358906.html
>
> Jerin
What's the status of your arm kernel patch?
Thanks,
Michael
>> Below are the details on modules, hugepages and device binding.
>> root@arm64:~# lsmod
>> Module Size Used by
>> rte_kni 292795 0
>> igb_uio 4338 0
>> ixgbe 184456 0
>>
>> root@arm64:~/dpdk# cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
>> 2048
>>
>> root@arm64:~/dpdk# ./tools/dpdk_nic_bind.py --status
>>
>> Network devices using DPDK-compatible driver
>> ============================================
>> 0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
>> drv=igb_uio unused=
>> 0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
>> drv=igb_uio unused=
>>
>> Network devices using kernel driver
>> ===================================
>> <none>
>>
>> Other network devices
>> =====================
>> <none>
>> root@arm64:~/dpdk#
>>
>> Thanks,
>> Ankit
next prev parent reply other threads:[~2016-01-14 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 10:22 Ankit Jindal
2016-01-14 3:08 ` Qiu, Michael
2016-01-14 4:15 ` Jerin Jacob
2016-01-14 8:26 ` Qiu, Michael [this message]
2016-01-14 11:12 ` Ankit Jindal
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=533710CFB86FA344BFBF2D6802E6028622F1870F@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=ajindal@apm.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jkanitkar@apm.com \
--cc=psawargaonkar@apm.com \
/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).