DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Rapelly, Varun" <vrapelly@sonusnet.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0
Date: Mon, 23 Mar 2015 10:57:31 +0000	[thread overview]
Message-ID: <BLUPR03MB264C49ABC6F32935F928D67B70D0@BLUPR03MB264.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20150320140234.GA5316@bricha3-MOBL3>

Hi Bruce,

Thanks for your reply.

I used dpdk_nic_bind.py script to bind igb_uio driver for the specific NIC ports. 

[root@SSBC swe]# ./ dpdk_nic_bind.py  --status

Network devices using IGB_UIO driver
====================================
0000:03:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3
0000:13:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3
0000:1b:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=vmxnet3

Network devices using kernel driver
===================================
0000:0b:00.0 'VMXNET3 Ethernet Controller' if=ha0 drv=vmxnet3 unused=igb_uio

When we ported to DPDK1.7.0, we didn't face this kind of issues.

When I googled, found similar problem. But didn't get any solution from that.
http://patchwork.dpdk.org/ml/archives/dev/2014-February/001437.html

Please give some directions to resolve this issue.

Regards,
Varun
-----Original Message-----
From: Bruce Richardson [mailto:bruce.richardson@intel.com] 
Sent: Friday, March 20, 2015 7:33 PM
To: Rapelly, Varun
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0

On Fri, Mar 20, 2015 at 07:09:00AM +0000, Rapelly, Varun wrote:
> 
> Hi All,
> 
> I'm facing the following issue when testing testpmd application with DPDK-1.8.0.
> 
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
> EAL:   0000:03:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:0b:00.0 on NUMA socket -1
> EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
> EAL:   0000:0b:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:13:00.0 on NUMA socket -1
> EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
> EAL:   0000:13:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:1b:00.0 on NUMA socket -1
> EAL:   probe driver: 15ad:7b0 rte_vmxnet3_pmd
> EAL:   0000:1b:00.0 not managed by UIO driver, skipping
> EAL: Error - exiting with code: 1
>   Cause: No probed ethernet device
> 
> Please let me know, what could be the issue.
> 
> FYI:
> Igb_uio and rte_kni ko modules are inserted successfully.

After you load the uio driver, you still need to bind some NIC devices to use it, otherwise DPDK will ignore those devices as being used by the kernel.
The script "dpdk_nic_bind.py" in the tools directory can help with the binding and unbinding to the different drivers.

/Bruce

> 
> Regards,
> Varun
> 

      reply	other threads:[~2015-03-23 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  7:09 Rapelly, Varun
2015-03-20 14:02 ` Bruce Richardson
2015-03-23 10:57   ` Rapelly, Varun [this message]

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=BLUPR03MB264C49ABC6F32935F928D67B70D0@BLUPR03MB264.namprd03.prod.outlook.com \
    --to=vrapelly@sonusnet.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /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).