* Re: [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0
@ 2015-03-20 7:09 Rapelly, Varun
2015-03-20 14:02 ` Bruce Richardson
0 siblings, 1 reply; 3+ messages in thread
From: Rapelly, Varun @ 2015-03-20 7:09 UTC (permalink / raw)
To: dev
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.
Regards,
Varun
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0
2015-03-20 7:09 [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0 Rapelly, Varun
@ 2015-03-20 14:02 ` Bruce Richardson
2015-03-23 10:57 ` Rapelly, Varun
0 siblings, 1 reply; 3+ messages in thread
From: Bruce Richardson @ 2015-03-20 14:02 UTC (permalink / raw)
To: Rapelly, Varun; +Cc: dev
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0
2015-03-20 14:02 ` Bruce Richardson
@ 2015-03-23 10:57 ` Rapelly, Varun
0 siblings, 0 replies; 3+ messages in thread
From: Rapelly, Varun @ 2015-03-23 10:57 UTC (permalink / raw)
To: Bruce Richardson; +Cc: dev
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-03-23 10:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-20 7:09 [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device with DPDK-1.8.0 Rapelly, Varun
2015-03-20 14:02 ` Bruce Richardson
2015-03-23 10:57 ` Rapelly, Varun
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).