Knowledge Base Article

Why is SMMU event 0x10 observed during AES-GCM decryption for payloads ≥ 4MB?

Description

Due to a problem between the ESW components and the memory subsystem, you may observe SMMU events on certain boards while running the FCS use case (AES GCM).

This problem does not impact the functionality of AES-GCM encryption or decryption.

 

The SMMU Event 0x10 was observed during AES-GCM decryption with payloads ≥ 4MB, using the following ESW components:

SW Component

Branch/tag/Version

Commit

LibFCS

main

5e394f8389c2e5c1a638058881e5c226fe9f7a51

Linux

socfpga-6.12.19-lts

7b88569116a96ce8323da2656c5a5018b920d9ff

 

 

 

 

 

Command used: 

root@agilex5dka5e065bb32aes1:~/run_dir/cs# ../fcs_client -Y -s 3296e0b8-e777-354a-8941-1e719cb803f5 -n 11 -k 35 -b 3 -m 0 -f iv.bin -u aad.bin --tag tag.bin -i data_4194304.bin -o aes_enc_10_4194304.out -v;../fcs_client -Y -s 3296e0b8-e777-354a-8941-1e719cb803f5 -n 11 -k 35 -b 3 -m 1 -f iv.bin -u aad.bin --tag tag.bin -i aes_enc_10_4194304.out -o aes_dec_10_4194304.out -v

AES Crypt successful

[  611.344327] arm-smmu-v3 16000000.iommu: event 0x10 received:

[  611.350162] arm-smmu-v3 16000000.iommu:      0x0000000a00000010

[  611.355779] arm-smmu-v3 16000000.iommu:      0x0000020a00000000

[  611.361404] arm-smmu-v3 16000000.iommu:      0x000000001fc00000

[  611.367034] arm-smmu-v3 16000000.iommu:      0x0000000000000000

AES Crypt successful

 

 

Resolution

This problem is scheduled to be fixed in a future release of the embedded software components.

Updated 11 months ago
Version 3.0
No CommentsBe the first to comment