[dpdk-dev] igb_uio binding issue

Pankaj Joshi pankaj.joshi63 at gmail.com
Mon Feb 1 12:59:09 CET 2016


Hello,

I am running DPDK sample application of l2_fwd.
I have some of the ports like ,

Network devices using IGB_UIO driver
====================================
0000:84:00.0 'I350 Gigabit Network Connection' drv=igb_uio unused=
0000:84:00.1 'I350 Gigabit Network Connection' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:05:00.0 'I350 Gigabit Network Connection' if=eth0 drv=igb
unused=igb_uio *Active*
0000:05:00.1 'I350 Gigabit Network Connection' if=eth1 drv=igb
unused=igb_uio
0000:06:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth4
drv=ixgbe unused=igb_uio
0000:06:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth5
drv=ixgbe unused=igb_uio
0000:0c:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth6
drv=ixgbe unused=igb_uio
0000:0c:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth7
drv=ixgbe unused=igb_uio
Other network devices
=====================
<none>

I have binded two port, but while running application it is searching for
ports which I have not binded.. Logs are showing as below :

EAL: Core 1 is ready (tid=cef5c700)
EAL: PCI device 0000:05:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   0000:05:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:05:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   0000:05:00.1 not managed by UIO driver, skipping
EAL: PCI device 0000:84:00.0 on NUMA socket 1
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   PCI memory mapped at 0x7f49d021a000
EAL:   PCI memory mapped at 0x7f49d0354000
EAL: PCI device 0000:84:00.1 on NUMA socket 1
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   PCI memory mapped at 0x7f49cd65a000
EAL:   PCI memory mapped at 0x7f49d0216000
Lcore 0: RX port 0
Lcore 1: RX port 1
Initializing port 0... EAL: Error - exiting with code: 1
  Cause: rte_eth_rx_queue_setup:err=-12, port=0

Can any one figure out the problem.

thanks,

Pankaj Joshi


More information about the dev mailing list