From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Port binding issues : NIC intel 82599ES
Date: Tue, 7 Feb 2017 22:24:03 +0530 [thread overview]
Message-ID: <CAGSp03mHubF1XcbxRAZBGvacU63DtV4jq77cNsLa2qNH406rrQ@mail.gmail.com> (raw)
Hi
I just started on dpdk, was trying to run l2fw. I bind two 82599 ports
using dpdk-devbind to igb_uio (first tried uio_pci_generic with same
result), then run l2fw but EAL is unable to probe these drivers still
getting ixgbe. Here is the console output
[root@unassigned build]# dpdk-devbind --status
Network devices using DPDK-compatible driver
============================================
0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio
unused=ixgbe,uio_pci_generic
0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio
unused=ixgbe,uio_pci_generic
Network devices using kernel driver
===================================
0000:02:00.0 'I210 Gigabit Network Connection' if=eno1 drv=igb
unused=igb_uio,uio_pci_generic
0000:03:00.0 'I210 Gigabit Network Connection' if=eno2 drv=igb
unused=igb_uio,uio_pci_generic
Other network devices
=====================
<none>
Crypto devices using DPDK-compatible driver
===========================================
<none>
Crypto devices using kernel driver
==================================
<none>
Other crypto devices
====================
<none>
[root@unassigned build]# ./l2fwd -c f -n 2 p ffff
EAL: Detected 8 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket -1
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:01:00.1 on NUMA socket -1
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:02:00.0 on NUMA socket -1
EAL: probe driver: 8086:1533 net_e1000_igb
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: probe driver: 8086:1533 net_e1000_igb
MAC updating enabled
Skipping disabled port 0
Skipping disabled port 1
EAL: Error - exiting with code: 1
Cause: All available ports are disabled. Please set portmask.
[root@unassigned build]#
next reply other threads:[~2017-02-07 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 16:54 Shyam Shrivastav [this message]
2017-02-23 11:37 Hristo.Trifonov
2017-02-23 12:14 ` Shyam Shrivastav
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=CAGSp03mHubF1XcbxRAZBGvacU63DtV4jq77cNsLa2qNH406rrQ@mail.gmail.com \
--to=shrivastav.shyam@gmail.com \
--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).