[dpdk-users] port 0 not present on board error

[Pragash Vijayaragavan]

I tried to debug by printing the check_port_config function

and printed the nb_ports parameter, -> this is 0

so i guess no ports are bind to the dpdk driver since its still showing
net_i40e in probe driver.

Should i do any config to solve this error.
i am using igb_uio and the ports are bind correctly, i bind using the
dpdk_dev_bind script.


pragash at revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-19
--no-huge -- -p 0x07 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
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: Requested device 0000:02:00.0 cannot be used
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: 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
L3FWD: IPV6 is specifiednsoft 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



Thanks,

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


On Mon, Dec 11, 2017 at 4:24 PM, Pragash Vijayaragavan <pxv3620 at g.rit.edu>
wrote:

> Hi,
>
> I am still getting some errors;
>
> port 0 is not present on the board.
>
> pragash at revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-4
> --no-huge -- -p 0x3 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
> EAL: Detected 20 lcore(s)
> EAL: Probing VFIO support...
> 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: Requested device 0000:02:00.0 cannot be used
> 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: 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
> L3FWD: IPV6 is specifiednsoft parse-ptype is enabled
> port 0 is not present on the board
> EAL: Error - exiting with code: 1
>   Cause: check_port_config failed
>
>
> Thanks,
>
> Pragash Vijayaragavan
> Grad Student at Rochester Institute of Technology
> email : pxv3620 at rit.edu
> ph : 585 764 4662 <(585)%20764-4662>
>
>
> On Mon, Dec 11, 2017 at 6:21 AM, Hristo.Trifonov <Hristo.Trifonov at ul.ie>
> wrote:
>
>> Not showing "Active" status is perfectly normal.
>>
>> The problem here is that you will probably need to supply extra
>> parameters.
>> This is from your previous posts:
>>
>> pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$
>> ./l3fwd -l 0-4 --no-huge -- -p 0x1
>>
>> Try changing to:
>>
>> pragash at revvit<http://dpdk.org/ml/listinfo/users>:~/dpdk-stable-17.05.2/examples/l3fwd/build$
>> ./l3fwd -l 1-4(core 0 is usually master lcore) --no-huge -- -p 0x3
>> -L(optional) -config="(0,0,1),(1,0,2)" --parse-type
>>
>>
>>
>> This worked for me. You can check the docs here
>> http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html for all options.
>>
>>
>> If you don't specify the "config" option the app won't even start
>> returning the "check port config" error. You must also supply the
>> "-parse-type" cmd parameter otherwise app complaints and fails to start
>> with the following error "port 0 cannot parse packet type, please add
>> -parse-type"
>>
>> Hristo T.
>>
>
>