LSDK20.04-isc-19 Memory Error

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

LSDK20.04-isc-19 Memory Error

Jump to solution
738 Views
Chidananda22
Contributor III

Hi All,

 

Previously I was using LSDK20.04-isc-09 . All running fine.

Now compiling my application with LSDK20.04-isc-19. Getting issue while pool creation .

It hangs . in GDB i can see stack corrupted .

compared . config and config/defconfig_arm64-dpaa-linuxapp-gcc.

Disabled : 

CONFIG_RTE_LA12XX_SOCKET_ID=0

CONFIG_RTE_LA12XX_SOCKET_MAX_SEG=0

 

Any memory and pool related changes I need to take care in my application.

Please suggest

Tags (1)
0 Kudos
Reply
1 Solution
661 Views
Chidananda22
Contributor III

Thanks @LFGP . 

 

Resolved after migrating to isc-23 . All application are up and running .

View solution in original post

0 Kudos
Reply
6 Replies
698 Views
Chidananda22
Contributor III

Hi @LFGP 

Verified with LSDK 21.08 . Same result. Stuck in memory allocation  .

Currently our application working fine with isc-09 . But while migrating to isc-19 it is stuck in memory allocation .

 

Working Logs

  • fslmc: fslmc_get_container_group(): Container: dprc.2 has VFIO iommu group id = 11
  • fslmc: fslmc_vfio_setup_group(): VFIO Container FD is [0x1D]
  • fslmc: fslmc_map_dma(): --> Map address: 0x140000000, size: 1073741824
  • fslmc: rte_fslmc_vfio_dmamap(): Installed memory callback handler
  • fslmc: rte_fslmc_vfio_dmamap(): Total 1 segments found.
  • fslmc: Unable to map region (errno = 22)

 

  • fslmc: dpaa2_get_qbman_swp(): New Portal 0x17ffec3c0 (2) affined thread - 2340
  • fslmc: dpaa2_configure_stashing(): Portal= 2  CPU= 3 SDEST= 1
  • fslmc: DPAA Portal=0x17ffec3c0 (2) is affined to thread 2340
  • fslmc: dpaa2_get_qbman_swp(): New Portal 0x17ffe4dc0 (3) affined thread - 2341
  • fslmc: dpaa2_configure_stashing(): Portal= 3  CPU= 2 SDEST= 1
  • fslmc: DPAA Portal=0x17ffe4dc0 (3) is affined to thread 2341
  • fslmc: fslmc_memevent_cb(): Request for alloc, va=0x1c0000000, virt_addr=0x1c0000000, iova=0x1c0000000, map_len=1073741824
  • fslmc: fslmc_map_dma(): --> Map address: 0x1c0000000, size: 1073741824
  • fslmc: fslmc_memevent_cb(): Total Mapped: addr=0x1c0000000, len=1073741824
  • fslmc: dpaa2_get_qbman_swp(): New Portal 0x17ffdd7c0 (4) affined thread - 2338
  • fslmc: dpaa2_configure_stashing(): Portal= 4  CPU= 1 SDEST= 0
  • fslmc: DPAA Portal=0x17ffdd7c0 (4) is affined for eth rx to thread 2338
  • fslmc: fslmc_memevent_cb(): Request for alloc, va=0x200000000, virt_addr=0x200000000, iova=0x200000000, map_len=1073741824

 

Not working Logs

  • fslmc: fslmc_get_group_id(): GROUP(dprc.2) has VFIO iommu group id = 11
  • fslmc: fslmc_vfio_setup_group(): VFIO GROUP FD is 28
  • fslmc: fslmc_map_dma(): DMA MEM map size(40000000): VA(140000000):IOVA(140000000):PHY(2700000000)
  • fslmc NOTICE: DMA MEM map size(40000000): VA(140000000):IOVA(140000000):PHY(2700000000)
  • fslmc: rte_fslmc_vfio_dmamap(): Installed memory callback handler
  • fslmc: rte_fslmc_vfio_dmamap(): Total 1 segments found.

Stuck Here

  • fslmc: fslmc_memevent_cb(): alloc, va=0x180000000, virt=180000000, iova=180000000, len=1073741824
  • fslmc: fslmc_map_dma(): DMA MEM map size(40000000): VA(180000000):IOVA(180000000):PHY(26c0000000)

 

recompiled again with

CONFIG_RTE_LA12XX_SOCKET_ID=0

CONFIG_RTE_LA12XX_SOCKET_MAX_SEG=0

 

No success . If any quick help based on above logs .

0 Kudos
Reply
685 Views
LFGP
NXP TechSupport
NXP TechSupport
dear @Chidananda22

please be sure regarding the free space to allocate the DMA.
On the other hand, please set the CONFIG_DEBUG_FS, CONFIG_DMA_API_DEBUG in the Kernel, in order to get out more info about the issue.
could you please share the complete logs for isc-09 and isc-19 as a compressed file.
0 Kudos
Reply
662 Views
Chidananda22
Contributor III

Thanks @LFGP . 

 

Resolved after migrating to isc-23 . All application are up and running .

0 Kudos
Reply
649 Views
LFGP
NXP TechSupport
NXP TechSupport
Dear @Chidananda22,

that is a great new, thanks for share your findings.
BR
LFGP
0 Kudos
Reply
698 Views
Chidananda22
Contributor III

 thanks @LFGP  for your quick response . I will use 21.08 LSDK and update you ,

0 Kudos
Reply
712 Views
LFGP
NXP TechSupport
NXP TechSupport

dear @Chidananda22 ,

there were several updates between  both releases (LSDK20.04-isc-09-Ubuntu 18 and  LSDK20.04-isc-19-Ubuntu20).

You need to upgrade your developer environment. Please considere to use the LSDK21.08 release.

BR

LFGP

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2161509%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ELSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2161509%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EPreviously%20I%20was%20using%26nbsp%3B%3CSPAN%3ELSDK20.04-isc-09%20.%20All%20running%20fine.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ENow%20compiling%20my%20application%20with%26nbsp%3BLSDK20.04-isc-19.%20Getting%20issue%20while%20pool%20creation%20.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20hangs%20.%20in%20GDB%20i%20can%20see%20stack%20corrupted%20.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ecompared%20.%20config%20and%26nbsp%3Bconfig%2Fdefconfig_arm64-dpaa-linuxapp-gcc.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EDisabled%20%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ECONFIG_RTE_LA12XX_SOCKET_ID%3D0%3C%2FP%3E%3CP%3ECONFIG_RTE_LA12XX_SOCKET_MAX_SEG%3D0%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EAny%20memory%20and%20pool%20related%20changes%20I%20need%20to%20take%20care%20in%20my%20application.%3C%2FP%3E%3CP%3EPlease%20suggest%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2164530%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2164530%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EDear%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F224905%22%20target%3D%22_blank%22%3E%40Chidananda22%3C%2FA%3E%2C%3CBR%20%2F%3E%3CBR%20%2F%3Ethat%20is%20a%20great%20new%2C%20thanks%20for%20share%20your%20findings.%3CBR%20%2F%3EBR%3CBR%20%2F%3ELFGP%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2164383%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2164383%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203371%22%20target%3D%22_blank%22%3E%40LFGP%3C%2FA%3E%26nbsp%3B.%26nbsp%3B%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EResolved%20after%20migrating%20to%20isc-23%20.%20All%20application%20are%20up%20and%20running%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2163032%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2163032%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3Edear%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F224905%22%20target%3D%22_blank%22%3E%40Chidananda22%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3Eplease%20be%20sure%20regarding%20the%20free%20space%20to%20allocate%20the%20DMA.%3CBR%20%2F%3EOn%20the%20other%20hand%2C%20please%20set%20the%20CONFIG_DEBUG_FS%2C%20CONFIG_DMA_API_DEBUG%20in%20the%20Kernel%2C%20in%20order%20to%20get%20out%20%20more%20info%20about%20the%20issue.%3CBR%20%2F%3Ecould%20you%20please%20share%20the%20complete%20logs%20for%20isc-09%20and%20isc-19%20as%20a%20compressed%20file.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2162187%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2162187%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203371%22%20target%3D%22_blank%22%3E%40LFGP%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVerified%20with%20LSDK%2021.08%20.%20Same%20result.%20Stuck%20in%20memory%20allocation%26nbsp%3B%20.%3C%2FP%3E%3CP%3ECurrently%20our%20application%20working%20fine%20with%20isc-09%20.%20But%20while%20migrating%20to%20isc-19%20it%20is%20stuck%20in%20memory%20allocation%20.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EWorking%20Logs%3C%2FP%3E%3CUL%3E%3CLI%3Efslmc%3A%20fslmc_get_container_group()%3A%20Container%3A%20dprc.2%20has%20VFIO%20iommu%20group%20id%20%3D%2011%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_vfio_setup_group()%3A%20VFIO%20Container%20FD%20is%20%5B0x1D%5D%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_map_dma()%3A%20--%26gt%3B%20Map%20address%3A%200x140000000%2C%20size%3A%201073741824%3C%2FLI%3E%3CLI%3Efslmc%3A%20rte_fslmc_vfio_dmamap()%3A%20Installed%20memory%20callback%20handler%3C%2FLI%3E%3CLI%3Efslmc%3A%20rte_fslmc_vfio_dmamap()%3A%20Total%201%20segments%20found.%3C%2FLI%3E%3CLI%3Efslmc%3A%20Unable%20to%20map%20region%20(errno%20%3D%2022)%3C%2FLI%3E%3C%2FUL%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3Efslmc%3A%20dpaa2_get_qbman_swp()%3A%20New%20Portal%200x17ffec3c0%20(2)%20affined%20thread%20-%202340%3C%2FLI%3E%3CLI%3Efslmc%3A%20dpaa2_configure_stashing()%3A%20Portal%3D%202%26nbsp%3B%20CPU%3D%203%20SDEST%3D%201%3C%2FLI%3E%3CLI%3Efslmc%3A%20DPAA%20Portal%3D0x17ffec3c0%20(2)%20is%20affined%20to%20thread%202340%3C%2FLI%3E%3CLI%3Efslmc%3A%20dpaa2_get_qbman_swp()%3A%20New%20Portal%200x17ffe4dc0%20(3)%20affined%20thread%20-%202341%3C%2FLI%3E%3CLI%3Efslmc%3A%20dpaa2_configure_stashing()%3A%20Portal%3D%203%26nbsp%3B%20CPU%3D%202%20SDEST%3D%201%3C%2FLI%3E%3CLI%3Efslmc%3A%20DPAA%20Portal%3D0x17ffe4dc0%20(3)%20is%20affined%20to%20thread%202341%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_memevent_cb()%3A%20Request%20for%20alloc%2C%20va%3D0x1c0000000%2C%20virt_addr%3D0x1c0000000%2C%20iova%3D0x1c0000000%2C%20map_len%3D1073741824%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_map_dma()%3A%20--%26gt%3B%20Map%20address%3A%200x1c0000000%2C%20size%3A%201073741824%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_memevent_cb()%3A%20Total%20Mapped%3A%20addr%3D0x1c0000000%2C%20len%3D1073741824%3C%2FLI%3E%3CLI%3Efslmc%3A%20dpaa2_get_qbman_swp()%3A%20New%20Portal%200x17ffdd7c0%20(4)%20affined%20thread%20-%202338%3C%2FLI%3E%3CLI%3Efslmc%3A%20dpaa2_configure_stashing()%3A%20Portal%3D%204%26nbsp%3B%20CPU%3D%201%20SDEST%3D%200%3C%2FLI%3E%3CLI%3Efslmc%3A%20DPAA%20Portal%3D0x17ffdd7c0%20(4)%20is%20affined%20for%20eth%20rx%20to%20thread%202338%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_memevent_cb()%3A%20Request%20for%20alloc%2C%20va%3D0x200000000%2C%20virt_addr%3D0x200000000%2C%20iova%3D0x200000000%2C%20map_len%3D1073741824%3C%2FLI%3E%3C%2FUL%3E%3CBR%20%2F%3E%3CP%3ENot%20working%20Logs%3C%2FP%3E%3CUL%3E%3CLI%3Efslmc%3A%20fslmc_get_group_id()%3A%20GROUP(dprc.2)%20has%20VFIO%20iommu%20group%20id%20%3D%2011%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_vfio_setup_group()%3A%20VFIO%20GROUP%20FD%20is%2028%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_map_dma()%3A%20DMA%20MEM%20map%20size(40000000)%3A%20VA(140000000)%3AIOVA(140000000)%3APHY(2700000000)%3C%2FLI%3E%3CLI%3Efslmc%20NOTICE%3A%20DMA%20MEM%20map%20size(40000000)%3A%20VA(140000000)%3AIOVA(140000000)%3APHY(2700000000)%3C%2FLI%3E%3CLI%3Efslmc%3A%20rte_fslmc_vfio_dmamap()%3A%20Installed%20memory%20callback%20handler%3C%2FLI%3E%3CLI%3Efslmc%3A%20rte_fslmc_vfio_dmamap()%3A%20Total%201%20segments%20found.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSTRONG%3E%3CU%3EStuck%20Here%20%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3Efslmc%3A%20fslmc_memevent_cb()%3A%20alloc%2C%20va%3D0x180000000%2C%20virt%3D180000000%2C%20iova%3D180000000%2C%20len%3D1073741824%3C%2FLI%3E%3CLI%3Efslmc%3A%20fslmc_map_dma()%3A%20DMA%20MEM%20map%20size(40000000)%3A%20VA(180000000)%3AIOVA(180000000)%3APHY(26c0000000)%3C%2FLI%3E%3C%2FUL%3E%3CBR%20%2F%3E%3CP%3Erecompiled%20again%20with%3C%2FP%3E%3CP%3ECONFIG_RTE_LA12XX_SOCKET_ID%3D0%3C%2FP%3E%3CP%3ECONFIG_RTE_LA12XX_SOCKET_MAX_SEG%3D0%3C%2FP%3E%3CBR%20%2F%3E%3CP%3ENo%20success%20.%20If%20any%20quick%20help%20based%20on%20above%20logs%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2162176%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2162176%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%26nbsp%3Bthanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203371%22%20target%3D%22_blank%22%3E%40LFGP%3C%2FA%3E%26nbsp%3B%20for%20your%20quick%20response%20.%20I%20will%20use%2021.08%20LSDK%20and%20update%20you%20%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2161637%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LSDK20.04-isc-19%20Memory%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2161637%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3Edear%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F224905%22%20target%3D%22_blank%22%3E%40Chidananda22%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3Ethere%20were%20several%20updates%20between%26nbsp%3B%20both%20releases%20(%3CSPAN%3ELSDK20.04-isc-09-Ubuntu%2018%20and%26nbsp%3B%26nbsp%3BLSDK20.04-isc-19-Ubuntu20).%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EYou%20need%20to%20upgrade%20your%20developer%20environment.%20Please%20considere%20to%20use%20the%20LSDK21.08%20release.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EBR%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ELFGP%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E