[IMX8MP] caam.jr and memory leak problems will occur when writing files to encrypted storage

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

[IMX8MP] caam.jr and memory leak problems will occur when writing files to encrypted storage

Jump to solution
1,172 Views
ZongYue
Contributor I

Hi,

When I use 8MPLUS-BB EVM with Yocto SDK imx-5.15.71-2.2.2 to do encrypted storage testing, it will happen below error:

[  599.799860] caam_jr 30902000.jr: unable to map source
[  599.799860] caam_jr 30902000.jr: unable to map destination
[  599.799856] swiotlb_tbl_map_single: 29 callbacks suppressed
[  599.799871] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32766 (slots)
[  599.807733] sdhci-esdhc-imx 30b60000.mmc: swiotlb buffer is full (sz: 4096 bytes), total 32768 (slots), used 32747 (slots)
[  599.810472] caam_jr 30902000.jr: unable to map destination
[  599.811862] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32768 (slots)
[  599.811875] caam_jr 30902000.jr: unable to map destination
[  599.817845] sdhci-esdhc-imx 30b60000.mmc: swiotlb buffer is full (sz: 4096 bytes), total 32768 (slots), used 32716 (slots)
[  599.825010] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32768 (slots)
[  599.825028] caam_jr 30902000.jr: unable to map destination
[  599.829011] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32739 (slots)
[  599.830025] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32768 (slots)
[  599.830037] caam_jr 30902000.jr: unable to map source
[  599.830473] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32768 (slots)
[  599.830480] caam_jr 30902000.jr: unable to map destination
[  599.832220] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32768 (slots)
[  599.832243] caam_jr 30902000.jr: unable to map source
[  599.832297] caam_jr 30902000.jr: swiotlb buffer is full (sz: 512 bytes), total 32768 (slots), used 32768 (slots)
[  599.832303] caam_jr 30902000.jr: unable to map source
[  599.956856] caam_jr 30902000.jr: unable to map source
[  600.020029] EXT4-fs warning: 2 callbacks suppressed
[  600.020043] EXT4-fs warning (device dm-0): ext4_end_bio:344: I/O error 10 writing to inode 12 starting block 254977)
[  600.035480] buffer_io_error: 24566 callbacks suppressed
[  600.035486] Buffer I/O error on device dm-0, logical block 253953
[  600.046797] Buffer I/O error on device dm-0, logical block 253954
[  600.052887] Buffer I/O error on device dm-0, logical block 253955
[  600.058976] Buffer I/O error on device dm-0, logical block 253956
[  600.065091] Buffer I/O error on device dm-0, logical block 253957
[  600.071183] Buffer I/O error on device dm-0, logical block 253958
[  600.077274] Buffer I/O error on device dm-0, logical block 253959
[  600.083364] Buffer I/O error on device dm-0, logical block 253960
[  600.089475] Buffer I/O error on device dm-0, logical block 253961
[  600.095569] Buffer I/O error on device dm-0, logical block 253962
[  600.113708] EXT4-fs warning (device dm-0): ext4_end_bio:344: I/O error 10 writing to inode 12 starting block 259073)
[  600.126834] EXT4-fs warning (device dm-0): ext4_end_bio:344: I/O error 10 writing to inode 12 starting block 257025)
[  600.139537] EXT4-fs warning (device dm-0): ext4_end_bio:344: I/O error 10 writing to inode 12 starting block 80897)
[  600.151162] EXT4-fs warning (device dm-0): ext4_end_bio:344: I/O error 10 writing to inode 12 starting block 78849)
[  600.185542] EXT4-fs warning (device dm-0): ext4_end_bio:344: I/O error 10 writing to inode 12 starting block 76801)
[  600.197689] JBD2: Detected IO errors while flushing file data on dm-0-8

 And system memory will leak.

I put the test log as attachment.

Wondering if there are any limitations to using encrypted storage feature?

0 Kudos
Reply
1 Solution
1,147 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi, 

This should be a known issue, suggest to test with newer BSP, l just get a chance of testing the same with BSP 6.6.3 and without such issue.

Also you can have a reference for the BSP 5.15 with this link

 

Regards

Harvey 

View solution in original post

0 Kudos
Reply
3 Replies
1,148 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi, 

This should be a known issue, suggest to test with newer BSP, l just get a chance of testing the same with BSP 6.6.3 and without such issue.

Also you can have a reference for the BSP 5.15 with this link

 

Regards

Harvey 

0 Kudos
Reply
1,143 Views
ZongYue
Contributor I

Hi @Harvey021 ,

Thank you,  I will update with any news soon.

I would also like to ask if CAAM is suitable for situations where there is only 1GB of RAM.
From the article, most of them use more than 2GB of RAM.

0 Kudos
Reply
1,138 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi @ZongYue 

I'm not sure about the correlation. 

 

Regards

Harvey

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2020457%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%5BIMX8MP%5D%20caam.jr%20and%20memory%20leak%20problems%20will%20occur%20when%20writing%20files%20to%20encrypted%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020457%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EWhen%20I%20use%208MPLUS-BB%20EVM%20with%20Yocto%20SDK%20imx-5.15.71-2.2.2%20to%20do%20encrypted%20storage%20testing%2C%20it%20will%20happen%20below%20error%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-c%22%3E%3CCODE%3E%5B%20%20599.799860%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20source%0A%5B%20%20599.799860%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20destination%0A%5B%20%20599.799856%5D%20swiotlb_tbl_map_single%3A%2029%20callbacks%20suppressed%0A%5B%20%20599.799871%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032766%20(slots)%0A%5B%20%20599.807733%5D%20sdhci-esdhc-imx%2030b60000.mmc%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%204096%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032747%20(slots)%0A%5B%20%20599.810472%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20destination%0A%5B%20%20599.811862%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032768%20(slots)%0A%5B%20%20599.811875%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20destination%0A%5B%20%20599.817845%5D%20sdhci-esdhc-imx%2030b60000.mmc%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%204096%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032716%20(slots)%0A%5B%20%20599.825010%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032768%20(slots)%0A%5B%20%20599.825028%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20destination%0A%5B%20%20599.829011%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032739%20(slots)%0A%5B%20%20599.830025%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032768%20(slots)%0A%5B%20%20599.830037%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20source%0A%5B%20%20599.830473%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032768%20(slots)%0A%5B%20%20599.830480%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20destination%0A%5B%20%20599.832220%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032768%20(slots)%0A%5B%20%20599.832243%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20source%0A%5B%20%20599.832297%5D%20caam_jr%2030902000.jr%3A%20swiotlb%20buffer%20is%20full%20(sz%3A%20512%20bytes)%2C%20total%2032768%20(slots)%2C%20used%2032768%20(slots)%0A%5B%20%20599.832303%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20source%0A%5B%20%20599.956856%5D%20caam_jr%2030902000.jr%3A%20unable%20to%20map%20source%0A%5B%20%20600.020029%5D%20EXT4-fs%20warning%3A%202%20callbacks%20suppressed%0A%5B%20%20600.020043%5D%20EXT4-fs%20warning%20(device%20dm-0)%3A%20ext4_end_bio%3A344%3A%20I%2FO%20error%2010%20writing%20to%20inode%2012%20starting%20block%20254977)%0A%5B%20%20600.035480%5D%20buffer_io_error%3A%2024566%20callbacks%20suppressed%0A%5B%20%20600.035486%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253953%0A%5B%20%20600.046797%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253954%0A%5B%20%20600.052887%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253955%0A%5B%20%20600.058976%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253956%0A%5B%20%20600.065091%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253957%0A%5B%20%20600.071183%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253958%0A%5B%20%20600.077274%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253959%0A%5B%20%20600.083364%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253960%0A%5B%20%20600.089475%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253961%0A%5B%20%20600.095569%5D%20Buffer%20I%2FO%20error%20on%20device%20dm-0%2C%20logical%20block%20253962%0A%5B%20%20600.113708%5D%20EXT4-fs%20warning%20(device%20dm-0)%3A%20ext4_end_bio%3A344%3A%20I%2FO%20error%2010%20writing%20to%20inode%2012%20starting%20block%20259073)%0A%5B%20%20600.126834%5D%20EXT4-fs%20warning%20(device%20dm-0)%3A%20ext4_end_bio%3A344%3A%20I%2FO%20error%2010%20writing%20to%20inode%2012%20starting%20block%20257025)%0A%5B%20%20600.139537%5D%20EXT4-fs%20warning%20(device%20dm-0)%3A%20ext4_end_bio%3A344%3A%20I%2FO%20error%2010%20writing%20to%20inode%2012%20starting%20block%2080897)%0A%5B%20%20600.151162%5D%20EXT4-fs%20warning%20(device%20dm-0)%3A%20ext4_end_bio%3A344%3A%20I%2FO%20error%2010%20writing%20to%20inode%2012%20starting%20block%2078849)%0A%5B%20%20600.185542%5D%20EXT4-fs%20warning%20(device%20dm-0)%3A%20ext4_end_bio%3A344%3A%20I%2FO%20error%2010%20writing%20to%20inode%2012%20starting%20block%2076801)%0A%5B%20%20600.197689%5D%20JBD2%3A%20Detected%20IO%20errors%20while%20flushing%20file%20data%20on%20dm-0-8%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3BAnd%20system%20memory%20will%20leak.%3C%2FP%3E%3CP%3EI%20put%20the%20test%20log%20as%20attachment.%3C%2FP%3E%3CP%3EWondering%20if%20there%20are%20any%20limitations%20to%20using%20encrypted%20storage%20feature%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2020457%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3Ei.MX%208%20Family%20%7C%20i.MX%208QuadMax%20(8QM)%20%7C%208QuadPlus%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ei.MX%208M%20%7C%20i.MX%208M%20Mini%20%7C%20i.MX%208M%20Nano%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYocto%20Project%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2020723%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20%5BIMX8MP%5D%20caam.jr%20and%20memory%20leak%20problems%20will%20occur%20when%20writing%20files%20to%20encrypted%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020723%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%2F221888%22%20target%3D%22_blank%22%3E%40ZongYue%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI'm%20not%20sure%20about%20the%20correlation.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3ERegards%3C%2FP%3E%0A%3CP%3EHarvey%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2020690%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20%5BIMX8MP%5D%20caam.jr%20and%20memory%20leak%20problems%20will%20occur%20when%20writing%20files%20to%20encrypted%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020690%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%2F192970%22%20target%3D%22_blank%22%3E%40Harvey021%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%2C%26nbsp%3B%20I%20will%20update%20with%20any%20news%20soon.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20would%20also%20like%20to%20ask%20if%20CAAM%20is%20suitable%20for%20situations%20where%20there%20is%20only%201GB%20of%20RAM.%3CBR%20%2F%3EFrom%20the%20article%2C%20most%20of%20them%20use%20more%20than%202GB%20of%20RAM.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2020675%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20%5BIMX8MP%5D%20caam.jr%20and%20memory%20leak%20problems%20will%20occur%20when%20writing%20files%20to%20encrypted%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020675%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20should%20be%20a%20known%20issue%2C%20suggest%20to%20test%20with%20newer%20BSP%2C%20l%20just%20get%20a%20chance%20of%20testing%20the%20same%20with%20BSP%206.6.3%20and%20without%20such%20issue.%3C%2FP%3E%0A%3CP%3EAlso%20you%20can%20have%20a%20reference%20for%20the%20BSP%205.15%20with%20this%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fi-MX-Processors%2Fquot-swiotlb-buffer-is-full-quot-when-writing-large-file-on%2Fm-p%2F1586218%22%20target%3D%22_self%22%3Elink%3C%2FA%3E%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3ERegards%3C%2FP%3E%0A%3CP%3EHarvey%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E