DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Rapelly, Varun" <vrapelly@sonusnet.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Testpmd application failing with Cause: No probed ethernet device
Date: Fri, 20 Mar 2015 06:34:24 +0000	[thread overview]
Message-ID: <BLUPR03MB264EB69626A3417C5A0EC27B70E0@BLUPR03MB264.namprd03.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hi All,

I'm facing the following issue when testing testpmd application.

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


[-- Attachment #2: test_pmd_log.txt --]
[-- Type: text/plain, Size: 3775 bytes --]

[root@SSBC dpdk]# insmod ~/igb_uio.ko 
[root@SSBC dpdk]# insmod ~/rte_kni.ko 
[root@SSBC dpdk]# cd
[root@SSBC ~]# ./testpmd -c 0xf -n 1
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fb798000000 (size = 0x200000)
EAL: Ask a virtual area of 0x71400000 bytes
EAL: Virtual area found at 0x7fb726a00000 (size = 0x71400000)
EAL: Ask a virtual area of 0x4400000 bytes
EAL: Virtual area found at 0x7fb722400000 (size = 0x4400000)
EAL: Ask a virtual area of 0xa400000 bytes
EAL: Virtual area found at 0x7fb717e00000 (size = 0xa400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fb717a00000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~2893029 KHz
EAL: Master core 0 is ready (tid=994a3800)
PMD: ENICPMD trace: rte_enic_pmd_init
EAL: Core 3 is ready (tid=15df0700)
EAL: Core 2 is ready (tid=165f1700)
EAL: Core 1 is ready (tid=16df2700)
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
[root@SSBC ~]# dmesg |grep varun
[root@SSBC ~]# ./testpmd -c 0xf -n 1
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0990e00000 (size = 0x200000)
EAL: Ask a virtual area of 0x71400000 bytes
EAL: Virtual area found at 0x7f091f800000 (size = 0x71400000)
EAL: Ask a virtual area of 0x4400000 bytes
EAL: Virtual area found at 0x7f091b200000 (size = 0x4400000)
EAL: Ask a virtual area of 0xa400000 bytes
EAL: Virtual area found at 0x7f0910c00000 (size = 0xa400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0910800000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~2893029 KHz
EAL: Master core 0 is ready (tid=923da800)
PMD: ENICPMD trace: rte_enic_pmd_init
EAL: Core 3 is ready (tid=ebf0700)
EAL: Core 2 is ready (tid=f3f1700)
EAL: Core 1 is ready (tid=fbf2700)
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

                 reply	other threads:[~2015-03-20  6:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BLUPR03MB264EB69626A3417C5A0EC27B70E0@BLUPR03MB264.namprd03.prod.outlook.com \
    --to=vrapelly@sonusnet.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).