topic ls1043 run dpdk l2fwd sample error in Layerscape

ls1043 run dpdk l2fwd sample error

lixiaofan — Wed, 18 Sep 2019 08:31:37 GMT

ls1043 run dpdk l2fwd sample error

#l2fwd -c 0x2 -n 1 -- -p 0x1 -q 1 -T 0

EAL: Detected 2 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: DPAA Bus Detected
PMD: Using FMC script mode,Make sure to use DPDK supported FMC scripts only.
l2fwd: process_portal_map(): Unknown error -19
dpaa: bman_thread_init failed on core 1 (lcore=1) with ret: -19
rte_dpaa_probe(): Unable to initialize portal
dpaa: Unable to probe.

l2fwd: process_portal_map(): Unknown error -19
dpaa: bman_thread_init failed on core 1 (lcore=1) with ret: -19
rte_dpaa_probe(): Unable to initialize portal
dpaa: Unable to probe.

dpaa_sec: qman_create_fq failed
dpaa_sec: config tx of queue pair 0
dpaa_sec: driver dpaa_sec-5: create failed

EAL: Error: Invalid memory
dpaa: Unable to probe.

dpaa_sec: qman_create_fq failed
dpaa_sec: config tx of queue pair 0
dpaa_sec: driver dpaa_sec-5: create failed

EAL: Error: Invalid memory
CRYPTODEV: rte_cryptodev_close() line 909: Invalid dev_id=0
dpaa: Unable to probe.

dpaa_sec: qman_create_fq failed
dpaa_sec: config tx of queue pair 0
dpaa_sec: driver dpaa_sec-5: create failed

EAL: Error: Invalid memory
CRYPTODEV: rte_cryptodev_close() line 909: Invalid dev_id=0
dpaa: Unable to probe.

dpaa_sec: qman_create_fq failed
dpaa_sec: config tx of queue pair 0
dpaa_sec: driver dpaa_sec-5: create failed

EAL: Error: Invalid memory
CRYPTODEV: rte_cryptodev_close() line 909: Invalid dev_id=0
dpaa: Unable to probe.

MAC updating enabled
EAL: Error - exiting with code: 1
Cause: No Ethernet ports - bye

Re: ls1043 run dpdk l2fwd sample error

yipingwang — Thu, 19 Sep 2019 05:58:56 GMT

Hello Xiaofan Lee,

Please refer to the following procedure to set up DPDK l2fwd.

1. Please boot up the target board with DPDK specific Device Tree file fsl-ls1043a-rdb-usdpaa.dtb.

2. Please configure bootargs as the following.

setenv bootargs "console=ttyS0,115200 root=/dev/mmcblk0p3 rw rootwait earlycon=uart8250,mmio,0x21c0500 default_hugepagesz=2MB hugepagesz=2MB hugepages=448 isolcpus=1-3 bportals=s0 qportals=s0 iommu.passthrough=1"

3. Setup DPAA environment

# fmc -x
# fmc -c ./usdpaa_config_ls1043.xml -p ./usdpaa_policy_hash_ipv4_1queue.xml -a

4. # l2fwd -c 0x2 -n 1 -- -p 0x1 -q 1 -T 0

If your problem remains, please provide more detailed information.

Which version LSDK are you using?

Would you please attach your Linux console log including Linux Kernel booting up log and all your operations?

Thanks,

Yiping

Re: ls1043 run dpdk l2fwd sample error

lixiaofan — Fri, 20 Sep 2019 03:34:39 GMT

yipingwang‌

Hi YiPing,

Thanks for your help, now I can setup l2fwd dpdk sample, next step I want to use vpp, according LSDK-KC-REV18.12.pdf 9.3.4,

LS1046 and LS1043 Board setup:
— mkdir /mnt/hugepages
— mount -t hugetlbfs none /mnt/hugepages
— echo 256 > /proc/sys/vm/nr_hugepages

root@localhost:/usr/local/nxp/dpaa# vpp -c /etc/startup.conf
vlib_plugin_early_init:361: plugin path /usr/local/lib/vpp_plugins
load_one_plugin:117: Plugin disabled (default): abf_plugin.so
load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:117: Plugin disabled (default): avf_plugin.so
load_one_plugin:117: Plugin disabled (default): cdp_plugin.so
load_one_plugin:189: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit (DPDK))
load_one_plugin:117: Plugin disabled (default): flowprobe_plugin.so
load_one_plugin:117: Plugin disabled (default): gbp_plugin.so
load_one_plugin:117: Plugin disabled (default): gtpu_plugin.so
load_one_plugin:117: Plugin disabled (default): igmp_plugin.so
load_one_plugin:117: Plugin disabled (default): ila_plugin.so
load_one_plugin:117: Plugin disabled (default): ioam_plugin.so
load_one_plugin:117: Plugin disabled (default): ixge_plugin.so
load_one_plugin:117: Plugin disabled (default): l2e_plugin.so
load_one_plugin:117: Plugin disabled (default): lacp_plugin.so
load_one_plugin:117: Plugin disabled (default): lb_plugin.so
load_one_plugin:117: Plugin disabled (default): mactime_plugin.so
load_one_plugin:117: Plugin disabled (default): map_plugin.so
load_one_plugin:117: Plugin disabled (default): memif_plugin.so
load_one_plugin:189: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:117: Plugin disabled (default): nsh_plugin.so
load_one_plugin:117: Plugin disabled (default): nsim_plugin.so
load_one_plugin:117: Plugin disabled (default): perfmon_plugin.so
load_one_plugin:117: Plugin disabled (default): pppoe_plugin.so
load_one_plugin:117: Plugin disabled (default): srv6ad_plugin.so
load_one_plugin:117: Plugin disabled (default): srv6am_plugin.so
load_one_plugin:117: Plugin disabled (default): srv6as_plugin.so
load_one_plugin:117: Plugin disabled (default): stn_plugin.so
load_one_plugin:117: Plugin disabled (default): svs_plugin.so
load_one_plugin:117: Plugin disabled (default): tlsopenssl_plugin.so
load_one_plugin:117: Plugin disabled (default): unittest_plugin.so
load_one_plugin:117: Plugin disabled (default): vmxnet3_plugin.so
vpp[3106]: clib_elf_parse_file: open `/usr/local/bin/vpp': No such file or directory
vpp[3106]: clib_elf_parse_file: open `linux-vdso.so.1': No such file or directory
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: stn_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: memif_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: cdp_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: vmxnet3_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: flowprobe_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: avf_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: acl_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: gtpu_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: pppoe_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: nsh_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: dpdk_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: lacp_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: ioam_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: mactime_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: lb_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: nat_test_plugin.so
vpp[3106]: load_one_vat_plugin:67: Loaded plugin: nsim_test_plugin.so
vpp[3106]: received signal SIGSEGV, PC unsupported, faulting address 0x80000
Aborted

my startup.conf as below:

root@localhost:/usr/local/nxp/dpaa# cat /etc/startup.conf
heapsize 128M

unix {
nodaemon
log /tmp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
exec ./cmd.txt
}

api-trace {
## This stanza controls binary API tracing. Unless there is a very strong reason,
## please leave this feature enabled.
on
## Additional parameters:
##
## To set the number of binary API trace records in the circular buffer, configure nitems
##
## nitems <nnn>
##
## To save the api message table decode tables, configure a filename. Results in /tmp/<filename>
## Very handy for understanding api message changes between versions, identifying missing
## plugins, and so forth.
##
## save-api-table <filename>
}

#api-segment {
# gid vpp
#}

#socksvr {
# default
#}

cpu {
## In the VPP there is one main thread and optionally the user can create worker(s)
## The main thread and worker thread(s) can be pinned to CPU core(s) manually or automatically

## Manual pinning of thread(s) to CPU core(s)

## Set logical CPU core where main thread runs, if main core is not set
## VPP will use core 1 if available
main-core 0

## Set logical CPU core(s) where worker threads are running
# corelist-workers 2-3,18-19

## Automatic pinning of thread(s) to CPU core(s)

## Sets number of CPU core(s) to be skipped (1 ... N-1)
## Skipped CPU core(s) are not used for pinning main thread and working thread(s).
## The main thread is automatically pinned to the first available CPU core and worker(s)
## are pinned to next free CPU core(s) after core assigned to main thread
# skip-cores 4

## Specify a number of workers to be created
## Workers are pinned to N consecutive CPU cores while skipping "skip-cores" CPU core(s)
## and main thread's CPU core
workers 1

## Set scheduling policy and priority of main and worker threads

## Scheduling policy options are: other (SCHED_OTHER), batch (SCHED_BATCH)
## idle (SCHED_IDLE), fifo (SCHED_FIFO), rr (SCHED_RR)
# scheduler-policy fifo

## Scheduling priority is used only for "real-time policies (fifo and rr),
## and has to be in the range of priorities supported for a particular policy
# scheduler-priority 50
}

dpdk {
## Change default settings for all intefaces
huge-dir /mnt/hugepages
no-pci
num-mem-channels 1

#vdev crypto_armv8

## Crypto Protocol Offload will be Enabled by default
enable-lookaside-proto-offload

dev default {
## Number of receive queues, enables RSS
## Default is 1
num-rx-queues 1

# rss { ipv4 }

## Number of transmit queues, Default is equal
## to number of worker threads or 1 if no workers treads
num-tx-queues 1

## Number of descriptors in transmit and receive rings
## increasing or reducing number can impact performance
## Default is 1024 for both rx and tx
# num-rx-desc 512
# num-tx-desc 512

## VLAN strip offload mode for interface
## Default is off
# vlan-strip-offload on
}

## Whitelist specific interface by specifying PCI address
# dev 0000:02:00.0

## Blacklist specific device type by specifying PCI vendor:device
## Whitelist entries take precedence
# blacklist 8086:10fb

## Set interface name
# dev 0000:02:00.1 {
# name eth0
# }

## Whitelist specific interface by specifying PCI address and in
## addition specify custom parameters for this interface
# dev 0000:02:00.1 {
# num-rx-queues 2
# }

## Specify bonded interface and its slaves via PCI addresses
##
## Bonded interface in XOR load balance mode (mode 2) with L3 and L4 headers
# vdev eth_bond0,mode=2,slave=0000:02:00.0,slave=0000:03:00.0,xmit_policy=l34
# vdev eth_bond1,mode=2,slave=0000:02:00.1,slave=0000:03:00.1,xmit_policy=l34
##
## Bonded interface in Active-Back up mode (mode 1)
# vdev eth_bond0,mode=1,slave=0000:02:00.0,slave=0000:03:00.0
# vdev eth_bond1,mode=1,slave=0000:02:00.1,slave=0000:03:00.1

## Change UIO driver used by VPP, Options are: igb_uio, vfio-pci,
## uio_pci_generic or auto (default)
# uio-driver vfio-pci

## Disable multi-segment buffers, improves performance but
## disables Jumbo MTU support
# no-multi-seg

## Increase number of buffers allocated, needed only in scenarios with
## large number of interfaces and worker threads. Value is per CPU socket.
## Default is 16384
num-mbufs 8000

## Change hugepages allocation per-socket, needed only if there is need for
## larger number of mbufs. Default is 256M on each detected CPU socket
# socket-mem 2048,2048

## Disables UDP / TCP TX checksum offload. Typically needed for use
## faster vector PMDs (together with no-multi-seg)
# no-tx-checksum-offload

}

plugins {
## Adjusting the plugin path depending on where the VPP plugins are
# path /ws/vpp/build-root/install-vpp-native/vpp/lib/vpp_plugins

## Disable all plugins by default and then selectively enable specific plugins
plugin default { disable }
plugin dpdk_plugin.so { enable }
plugin acl_plugin.so { enable }
plugin nat_plugin.so { enable }

## Enable all plugins by default and then selectively disable specific plugins
# plugin dpdk_plugin.so { disable }
# plugin acl_plugin.so { disable }
}

any reply will be very appreciated, thanks!

Re: ls1043 run dpdk l2fwd sample error

yipingwang — Fri, 20 Sep 2019 05:32:09 GMT

Please create a new thread for your new problem.

Re: ls1043 run dpdk l2fwd sample error

pavel_meld — Fri, 15 Nov 2019 09:11:53 GMT

Have similar problem, tried to start kernel with specified arguments, but still can't resolve the problem =)

Is it possible to get SD-card image with all necessary things configured ?