Loading multiple vpps causes network disruption

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Loading multiple vpps causes network disruption

640 Views
linxs
Contributor I

Using the LX2160 chip under the Linux system

restool -v
restool v2.4 (10.30.0 compatible)

restool -m
MC firmware version: 10.36.0

ls-listni

dprc.1/dpni.0 (interface: eth0, end point: dpsw.0.1)
dprc.1/dprc.4/dpni.4 (end point: dpmac.9)
dprc.1/dprc.3/dpni.3 (end point: dpmac.7)
dprc.1/dprc.2/dpni.2 (end point: dpmac.6)
dprc.1/dprc.2/dpni.1 (end point: dpmac.5)

When I start vpp1 using dprc.3 and vpp2 using dprc.4, everything boots up normally, and the interface corresponding to dpni.0 works fine. However, when I start another PHY program using dprc.2, dpni.0 experiences abnormalities.

vpp1 and vpp2 allocated resources are DPCON_COUNT=8、DPBP_COUNT=16、DPMCP_COUNT=3、DPSECI_COUNT=16、DPIO_COUNT=4、DPCI_COUNT=4、DPDMAI_COUNT=4

phy program allocated resources are DPCON_COUNT=8、DPBP_COUNT=16、DPMCP_COUNT=3、DPSECI_COUNT=16、DPIO_COUNT=34、DPCI_COUNT=4、DPDMAI_COUNT=4

cat /dev/fsl_mc_console

[E, qbman_nrec_isr:421, QBMAN] QBMAN non-recoverable event 0x10
[E, enq_deq:68, CTLU] ifp_mng_cmd_try_dequeue() returned -EBUSY at each 1000 tries
[E, enq_deq:68, CTLU] ifp_mng_cmd_try_dequeue() returned -EBUSY at each 1000 tries
[E, enq_deq:68, CTLU] ifp_mng_cmd_try_dequeue() returned -EBUSY at each 1000 tries
[E, enq_deq:68, CTLU] ifp_mng_cmd_try_dequeue() returned -EBUSY at each 1000 tries
[E, dpni_add_mac_addr:10686, DPNI] ID[4]: Failed to add address
[E, ifp_mng_cmd_enqueue:1755, CTLU] Busy: No available Management command descriptor
[E, ifp_mng_cmd_enqueue:1755, CTLU] Busy: No available Management command descriptor

However, there are no issues when only one vpp and the PHY program are started. Why is that?

Is there any way to solve the problem?
Thanks for advice from experienced experts.
Regards!

 

0 Kudos
Reply
2 Replies

624 Views
LFGP
NXP TechSupport
NXP TechSupport
the issue you are facing due that the dpmac.5 is connected to the dpni.0 by default.
you can unbind it and then reassign it to other dpni.
please move out the dprc.4 ,3 and 2 from dprc.1
In order to get a better grasp review the subject "3.7.8.5 Bringing up DPAA2 network interfaces" in the LLDP reference manual
0 Kudos
Reply

616 Views
linxs
Contributor I

The creation of dpmac.5 is based on disconnecting and reconnecting .
And when tcpdump data from eth0 find another error:

fsl_dpaa2_eth dpni.0 eth0:Could not add mcast MAC 01:00:5e:00:00:01 to the filtering table(err -110).

 

0 Kudos
Reply