Issue with dpaa2 dpsw objects

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Issue with dpaa2 dpsw objects

3,767 次查看
Fa007
Contributor II

Hello,

I am using a DPAA2 dpsw and I have this error message below, can you please help me get rid of it ?

 

[Fri Mar 9 12:41:44 2018] fsl_dpaa2_switch dpsw.0 eth13: Link is Up - 1Gbps/Full - flow control rx
[Fri Mar 9 12:41:44 2018] br0: port 12(eth13) entered blocking state
[Fri Mar 9 12:41:44 2018] br0: port 12(eth13) entered forwarding state

 

[Fri Mar 9 12:41:55 2018] fsl_dpaa2_switch dpsw.0 eth13: failed (err=-6) to add object (id=2)
[Fri Mar 9 12:41:55 2018] fsl_dpaa2_switch dpsw.0 eth13: failed (err=-6) to add object (id=2)

 

LX2160A-RDB , DPAA2 

0 项奖励
回复
11 回复数

3,760 次查看
yipingwang
NXP TechSupport
NXP TechSupport

Please refer to the following procedure to use DPSW.

root@localhost:~# ls-addsw -i=4 dpmac.3 dpmac.4 dpmac.18 dpni.2
Created ETHSW object dpsw.0 with the following 4 ports: eth3,eth4,eth5,eth6
root@localhost:~# ls /sys/bus/fsl-mc/devices/dp
Display all 119 possibilities? (y or n)
root@localhost:~# ls /sys/bus/fsl-mc/devices/dpsw.0/net
eth3 eth4 eth5 eth6
root@localhost:~# ip link set dev eth3 down
root@localhost:~# ip link set dev eth3 address 5a:8d:bf:7c:5b:96
root@localhost:~# ip link set dev eth3 up
root@localhost:~# ip link set dev eth4 down
root@localhost:~# ip link set dev eth4 address 5a:8d:bf:7c:5b:97
root@localhost:~# ip link set dev eth4 up
root@localhost:~# ip link set dev eth5 down
root@localhost:~# ip link set dev eth5 address 5a:8d:bf:7c:5b:98
root@localhost:~# ip link set dev eth5 up
root@localhost:~# ip link set dev eth6 address 5a:8d:bf:7c:5b:99
root@localhost:~# ip link set dev eth6 up
root@localhost:~# ip link add name ethsw0 type bridge
root@localhost:~# ip link set ethsw0 up
root@localhost:~# ip link set eth3 master ethsw0
root@localhost:~# ip link set eth4 master ethsw0
root@localhost:~# ip link set eth5 master ethsw0
root@localhost:~# ip link set eth6 master ethsw0
root@localhost:~#
root@localhost:~# restool dpsw info dpsw.0
dpsw version: 8.12
dpsw id: 0
plugged state: plugged
endpoints:
interface 0:
connection: dpmac.3
link state: up
Taildrop enabled: false
Taildrop units: BUFFERS
Taildrop threshold: 192
max frame length: 1536
dpsw_cnt_ing_frame: 0
dpsw_cnt_ing_byte: 0
dpsw_cnt_ing_fltr_frame: 0
dpsw_cnt_ing_frame_discard: 0
dpsw_cnt_ing_mcast_frame: 0
dpsw_cnt_ing_mcast_byte: 0
dpsw_cnt_ing_bcast_frame: 0
dpsw_cnt_ing_bcast_bytes: 0
dpsw_cnt_egr_frame: 0
dpsw_cnt_egr_byte: 0
dpsw_cnt_egr_frame_discard: 0
dpsw_cnt_egr_stp_frame_discard: 0
dpsw_cnt_ing_no_buffer_discard: 0
interface 1:
connection: dpmac.4
link state: up
Taildrop enabled: false
Taildrop units: BUFFERS
Taildrop threshold: 192
max frame length: 1536
dpsw_cnt_ing_frame: 0
dpsw_cnt_ing_byte: 0
dpsw_cnt_ing_fltr_frame: 0
dpsw_cnt_ing_frame_discard: 0
dpsw_cnt_ing_mcast_frame: 0
dpsw_cnt_ing_mcast_byte: 0
dpsw_cnt_ing_bcast_frame: 0
dpsw_cnt_ing_bcast_bytes: 0
dpsw_cnt_egr_frame: 0
dpsw_cnt_egr_byte: 0
dpsw_cnt_egr_frame_discard: 0
dpsw_cnt_egr_stp_frame_discard: 0
dpsw_cnt_ing_no_buffer_discard: 0
interface 2:
connection: dpmac.18
link state: down
Taildrop enabled: false
Taildrop units: BUFFERS
Taildrop threshold: 192
max frame length: 1536
dpsw_cnt_ing_frame: 0
dpsw_cnt_ing_byte: 0
dpsw_cnt_ing_fltr_frame: 0
dpsw_cnt_ing_frame_discard: 0
dpsw_cnt_ing_mcast_frame: 0
dpsw_cnt_ing_mcast_byte: 0
dpsw_cnt_ing_bcast_frame: 0
dpsw_cnt_ing_bcast_bytes: 0
dpsw_cnt_egr_frame: 0
dpsw_cnt_egr_byte: 0
dpsw_cnt_egr_frame_discard: 0
dpsw_cnt_egr_stp_frame_discard: 0
dpsw_cnt_ing_no_buffer_discard: 0
interface 3:
connection: dpni.2
link state: down
Taildrop enabled: false
Taildrop units: BUFFERS
Taildrop threshold: 192
max frame length: 1536
dpsw_cnt_ing_frame: 0
dpsw_cnt_ing_byte: 0
dpsw_cnt_ing_fltr_frame: 0
dpsw_cnt_ing_frame_discard: 0
dpsw_cnt_ing_mcast_frame: 0
dpsw_cnt_ing_mcast_byte: 0
dpsw_cnt_ing_bcast_frame: 0
dpsw_cnt_ing_bcast_bytes: 0
dpsw_cnt_egr_frame: 0
dpsw_cnt_egr_byte: 0
dpsw_cnt_egr_frame_discard: 0
dpsw_cnt_egr_stp_frame_discard: 0
dpsw_cnt_ing_no_buffer_discard: 0
dpsw_attr.options value is: 0
max VLANs: 16
max FDBs: 1
max FDB entries: 1024
FDB aging time: 300
max FDB MC groups: 32
frame storage memory size: 1536
number of interfaces: 4
current number of VLANs: 1
current number of FDBs: 1
component_type: DPSW_COMPONENT_TYPE_C_VLAN

0 项奖励
回复

3,730 次查看
Fa007
Contributor II

Hi,


I have this error, when using restool to create a dpsw with 13x interface (12x dpmac and 1x internal dpni).

MC error: No memory available (status 0x9)

Do i need to increase the DPAA2 MC memory (mcmemsize) ?

0 项奖励
回复

3,671 次查看
yipingwang
NXP TechSupport
NXP TechSupport

This is due to default configuration of DPSW, the number of FDBs being 8.

If you limit the number of FDBs to 2, you will be able to create the DPSW with 63 interfaces.

Command : restool dpsw create --num-ifs=63 --max-fdbs=2.

0 项奖励
回复

3,658 次查看
Fa007
Contributor II

Hello,

 

You forgot to mention in your previous answer, the following:

ip link add dev br0 type bridge vlan_filtering 1

I needed to put the vlan_filtering 1 in there otherwise it does not work and we get an error.

 

If you look here: DPAA2 Switch driver — The Linux Kernel documentation

The minimum number of FDBs should be at least equal to the number of switch interfaces. This is necessary so that separation of switch ports can be done, ie when not under a bridge, each switch port will have its own FDB.

 

So I do not understand how i can put 2x FDB , i need a minimum of 13x FDB (since i have 12 DPMAC + 1 internal DPNI ) for the DPSW that i want to create.

 

Please can you help me here ? If i put 2x FDB , i do get an error :

fsl_dpaa2_switch dpsw.0: The number of FDBs is lower than the number of ports, cannot probe

 

0 项奖励
回复

3,657 次查看
Fa007
Contributor II
I am using the restool command : 

ls-addsw
  
0 项奖励
回复

3,607 次查看
yipingwang
NXP TechSupport
NXP TechSupport

I used LSDK 21.08 pre-built images, and didn't find any problem to run the following command.

root@TinyLinux:~# ls-addsw -i=13
[ 36.858020] fsl_mc_allocator dpbp.2: Adding to iommu group 10
[ 36.865610] fsl_mc_allocator dpmcp.36: Adding to iommu group 10
[ 36.873419] dpaa2_ethsw dpsw.0: Adding to iommu group 10
[ 37.057212] dpaa2_ethsw dpsw.0: probed 13 port switch
Created ETHSW object dpsw.0 with the following 13 ports: eth10,eth11,eth12,eth13,eth14,eth15,eth3,eth4,eth5,eth6,eth7,eth8,eth9
Do not forget to connect devices to interface(s).

0 项奖励
回复

3,594 次查看
Fa007
Contributor II

Hello,

You won't have the problem with the LSDK 21.08 as it is using an older MC firmware.

I am using NXP LLDP with MC version 10.38.0. Please try with that version.

 

mkdir -p yocto-ws && cd yocto-ws
repo init -u https://github.com/nxp-qoriq/yocto-sdk -b mickledore
repo sync --force-sync
 

Thanks.

标记 (1)
0 项奖励
回复

3,577 次查看
yipingwang
NXP TechSupport
NXP TechSupport

Please use the following command.

~# ls-addsw -i=13 --max-fdbs=2

Please refer to my attached console log.

0 项奖励
回复

3,456 次查看
Fa007
Contributor II

Hello,

The command you provided did not work.

You can tell that because the ethx print did not appear after you executed the command...

标记 (1)
0 项奖励
回复

3,439 次查看
yipingwang
NXP TechSupport
NXP TechSupport

Please address your current problem in a new thread.

0 项奖励
回复

3,455 次查看
Fa007
Contributor II
It should show the following output:
Created ETHSW object dpsw.0 with the following 13 ports: eth10,eth11,eth12,eth13,eth14,eth15,eth3,eth4,eth5,eth6,eth7,eth8,eth9
Do not forget to connect devices to interface(s).
0 项奖励
回复