DPDK usage discussions
 help / color / mirror / Atom feed
From: Pragash Vijayaragavan <pxv3620@rit.edu>
To: "Hristo.Trifonov" <Hristo.Trifonov@ul.ie>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] port 0 not present on board error
Date: Tue, 12 Dec 2017 08:33:53 -0500	[thread overview]
Message-ID: <CANp7S23eM=xVU+yFN-4YaJ52f2PH8vXG-U-4-vN+D7YwMHUJsg@mail.gmail.com> (raw)
In-Reply-To: <E6A390FF2129134EB58BFFFFDFFB5A844DFF28EB@ExMbx1.ul.campus>

This did not work as well.

Below is the error and config outputs


pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ sudo  ./l3fwd -c
0xE --no-huge -- -p 0x03 -L --config="(0,0,1),(1,0,2)" --parse-ptype
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.1 cannot be used
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
L3FWD: Longest-prefix match selected
soft parse-ptype is enabled
ports   ---- 0
port 0 is not present on the board
EAL: Error - exiting with code: 1
  Cause: check_port_config failed



Network devices using DPDK-compatible driver
============================================
0000:04:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci
0000:04:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
unused=vfio-pci

Network devices using kernel driver
===================================
0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=eth13
drv=i40e unused=igb_uio,vfio-pci
0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=eth12
drv=i40e unused=igb_uio,vfio-pci
0000:08:00.0 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb
unused=igb_uio,vfio-pci *Active*
0000:08:00.1 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb
unused=igb_uio,vfio-pci

Other Network devices
=====================
<none>




Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu
ph : 585 764 4662


On Tue, Dec 12, 2017 at 7:47 AM, Hristo.Trifonov <Hristo.Trifonov@ul.ie>
wrote:

> Please use only 2 ports with 1RX queue and 1 TX queue each to get l3fwd
> running. Try with these 2 below.
> 0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
> unused=vfio-pci
> 0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio
> unused=vfio-pci
>
> You can use more ports/queues but then you'll have to change the -config
> option depending on how many cores do you want to use.
>
> The cmd that I've provided in my previous post is specifically for 2 ports
> with 1RX and TX queue each and 2 cores.
>
> I suggest that you restart your machine, if possible, to unbind all ports
> from igb_uio and start from scratch.
> Otherwise use the dpdk-seup.py script to do the clean-up.
>
> Hristo T.
>
>

  reply	other threads:[~2017-12-12 13:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 12:47 Hristo.Trifonov
2017-12-12 13:33 ` Pragash Vijayaragavan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-12 14:02 Hristo.Trifonov
2017-12-12 14:13 ` Pragash Vijayaragavan
2017-12-12 10:54 Hristo.Trifonov
2017-12-12 12:21 ` Pragash Vijayaragavan
2017-12-11 11:21 Hristo.Trifonov
2017-12-11 21:24 ` Pragash Vijayaragavan
2017-12-12  6:17   ` Pragash Vijayaragavan
2017-12-12  7:17   ` Stephen Hemminger
2017-12-08 12:11 Hristo.Trifonov
2017-12-08 20:22 ` Pragash Vijayaragavan
2017-12-08  4:01 Pragash Vijayaragavan
2017-12-08  4:18 ` Dave Boutcher
2017-12-08  4:21   ` Pragash Vijayaragavan

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='CANp7S23eM=xVU+yFN-4YaJ52f2PH8vXG-U-4-vN+D7YwMHUJsg@mail.gmail.com' \
    --to=pxv3620@rit.edu \
    --cc=Hristo.Trifonov@ul.ie \
    --cc=users@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).