From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Pankaj Joshi <pankaj.joshi63@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] igb_uio binding issue
Date: Mon, 1 Feb 2016 12:26:33 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C89E072@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAOYs48GJ8EBrjhJav_KumgeJZ5M9gKZW1A187Op7ZV=6pTicGw@mail.gmail.com>
Hi Pankaj,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pankaj Joshi
> Sent: Monday, February 01, 2016 11:59 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] igb_uio binding issue
>
> Hello,
>
> I am running DPDK sample application of l2_fwd.
> I have some of the ports like ,
>
> Network devices using IGB_UIO driver
> ====================================
> 0000:84:00.0 'I350 Gigabit Network Connection' drv=igb_uio unused=
> 0000:84:00.1 'I350 Gigabit Network Connection' drv=igb_uio unused=
> Network devices using kernel driver
> ===================================
> 0000:05:00.0 'I350 Gigabit Network Connection' if=eth0 drv=igb
> unused=igb_uio *Active*
> 0000:05:00.1 'I350 Gigabit Network Connection' if=eth1 drv=igb
> unused=igb_uio
> 0000:06:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth4
> drv=ixgbe unused=igb_uio
> 0000:06:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth5
> drv=ixgbe unused=igb_uio
> 0000:0c:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth6
> drv=ixgbe unused=igb_uio
> 0000:0c:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth7
> drv=ixgbe unused=igb_uio
> Other network devices
> =====================
> <none>
>
> I have binded two port, but while running application it is searching for
> ports which I have not binded.. Logs are showing as below :
>
> EAL: Core 1 is ready (tid=cef5c700)
> EAL: PCI device 0000:05:00.0 on NUMA socket 0
> EAL: probe driver: 8086:1521 rte_igb_pmd
> EAL: 0000:05:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:05:00.1 on NUMA socket 0
> EAL: probe driver: 8086:1521 rte_igb_pmd
> EAL: 0000:05:00.1 not managed by UIO driver, skipping
> EAL: PCI device 0000:84:00.0 on NUMA socket 1
> EAL: probe driver: 8086:1521 rte_igb_pmd
> EAL: PCI memory mapped at 0x7f49d021a000
> EAL: PCI memory mapped at 0x7f49d0354000
> EAL: PCI device 0000:84:00.1 on NUMA socket 1
> EAL: probe driver: 8086:1521 rte_igb_pmd
> EAL: PCI memory mapped at 0x7f49cd65a000
> EAL: PCI memory mapped at 0x7f49d0216000
> Lcore 0: RX port 0
> Lcore 1: RX port 1
> Initializing port 0... EAL: Error - exiting with code: 1
> Cause: rte_eth_rx_queue_setup:err=-12, port=0
>
> Can any one figure out the problem.
>
As you can see in the log, DPDK got the ports that you bound to igb_uio, 84:00.x (the others have been skipped).
The problem is that it could not configure the devices properly.
Could you send the command line that you used?
Pablo
> thanks,
>
> Pankaj Joshi
next prev parent reply other threads:[~2016-02-01 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 11:59 Pankaj Joshi
2016-02-01 12:26 ` De Lara Guarch, Pablo [this message]
2016-02-01 14:19 ` Remy Horton
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=E115CCD9D858EF4F90C690B0DCB4D8973C89E072@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=pankaj.joshi63@gmail.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).