ls1023a kernel stuck once enabled the sdk's dpaa function within kernel config

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

ls1023a kernel stuck once enabled the sdk's dpaa function within kernel config

Jump to solution
1,218 Views
fduan
Contributor I

hi, 

 

During the kernel's boot-up, when enabled the follow function, kernel will stuck. kernel version is 4.14 and running with arm64 and kernel source code fetched as follow by Yocto from https://source.codeaurora.org/external/qoriq/qoriq-components/linux

{code}

CONFIG_FSL_SDK_DPAA_ETH=y
CONFIG_FSL_DPAA_OFFLINE_PORTS=y
CONFIG_FSL_DPAA_ADVANCED_DRIVERS=y
CONFIG_FSL_DPAA_ETH_USE_NDO_SELECT_QUEUE=y
CONFIG_FSL_DPAA_ETH_MAX_BUF_COUNT=128
CONFIG_FSL_DPAA_ETH_REFILL_THRESHOLD=80
CONFIG_FSL_DPAA_CS_THRESHOLD_1G=0x06000000
CONFIG_FSL_DPAA_CS_THRESHOLD_10G=0x10000000
CONFIG_FSL_DPAA_INGRESS_CS_THRESHOLD=0x10000000
CONFIG_FSL_DPAA_ETH_DEBUGFS=y
CONFIG_FSL_SDK_DPA=y
CONFIG_FSL_DPA_CAN_WAIT=y
CONFIG_FSL_DPA_CAN_WAIT_SYNC=y
CONFIG_FSL_DPA_PIRQ_FAST=y
CONFIG_FSL_DPA_PIRQ_SLOW=y
CONFIG_FSL_DPA_PORTAL_SHARE=y
CONFIG_FSL_USDPAA=y

{code}

 

And after reset the board, during u-boot, I dumped the __log_buf details, kernel run to follow:

{code}

=>
8134e738: 2e 00 00 00 10 c4 24 43 00 00 00 00 48 00 35 00 ......$C....H.5.
8134e748: 00 00 00 c6 44 4d 41 3a 20 70 72 65 61 6c 6c 6f ....DMA: preallo
8134e758: 63 61 74 65 64 20 32 35 36 20 4b 69 42 20 70 6f cated 256 KiB po
8134e768: 6f 6c 20 66 6f 72 20 61 74 6f 6d 69 63 20 61 6c ol for atomic al
=>
8134e778: 6c 6f 63 61 74 69 6f 6e 73 00 00 00 e0 34 2f 43 locations....4/C
8134e788: 00 00 00 00 28 00 16 00 00 00 00 c6 4d 61 63 68 ....(.......Mach
8134e798: 69 6e 65 3a 20 4c 61 6e 67 6c 65 79 20 42 6f 61 ine: Langley Boa
8134e7a8: 72 64 00 00 f8 44 2f 43 00 00 00 00 2c 00 19 00 rd...D/C....,...
=>
8134e7b8: 00 00 00 c6 53 6f 43 20 66 61 6d 69 6c 79 3a 20 ....SoC family:
8134e7c8: 51 6f 72 49 51 20 4c 53 31 30 34 33 41 00 00 00 QorIQ LS1043A...
8134e7d8: 58 53 2f 43 00 00 00 00 38 00 25 00 00 00 00 c6 XS/C....8.%.....
8134e7e8: 53 6f 43 20 49 44 3a 20 73 76 72 3a 30 78 38 37 SoC ID: svr:0x87
=>
8134e7f8: 39 32 30 62 31 31 2c 20 52 65 76 69 73 69 6f 6e 920b11, Revision
8134e808: 3a 20 31 2e 31 00 00 00 d0 52 cb 43 00 00 00 00 : 1.1....R.C....
8134e818: 4c 00 3c 00 00 00 00 c6 48 75 67 65 54 4c 42 20 L.<.....HugeTLB
8134e828: 72 65 67 69 73 74 65 72 65 64 20 32 2e 30 30 20 registered 2.00
=>
8134e838: 4d 69 42 20 70 61 67 65 00 00 00 00 00 00 00 00 MiB page........

{code}

 

If I disabled the DPAA function by setting "CONFIG_FSL_SDK_DPA=n" , kernel bootup successfully,  kernel is running with arm64. 

 

BR

Fisher Duan

 

Labels (1)
0 Kudos
Reply
1 Solution
1,204 Views
teddy_gom_e
Contributor III

Hi,

I recently (friday) switched from USDPAA to DPAA SDK, my kernel config is the same as your, my kernel is booting.

 

Check your DTS file and use inspiration from fsl-ls1043a-rdb-sdk.dts, configuration  is really different from fsl-ls1043a-rdb-usdpaa.dts. I had a segfault in kernel, changing the configuration resolved (for the moment) everything

View solution in original post

0 Kudos
Reply
1 Reply
1,205 Views
teddy_gom_e
Contributor III

Hi,

I recently (friday) switched from USDPAA to DPAA SDK, my kernel config is the same as your, my kernel is booting.

 

Check your DTS file and use inspiration from fsl-ls1043a-rdb-sdk.dts, configuration  is really different from fsl-ls1043a-rdb-usdpaa.dts. I had a segfault in kernel, changing the configuration resolved (for the moment) everything

0 Kudos
Reply