iMX8MM CAAM errors when using 'tk(cbc(aes))' for filesystem encryption

[djs2]

I'm getting the following error when writing to a filesystem using the CAAM for filesystem encryption with `tk(cbc(aes))`.

caam_jr 30902000.jr: 4000141c: DECO: desc idx 20: DECO Watchdog timer timeout error

This only happens occasionally but seems to be more prevalent when running with all cores enabled.

[djs2]

Unfortunately, I've been unable to reproduce with other tools

I have added logging of last 2048 CAAM log messages on failure and we are now waiting for failure to re-occur in CI.  I'll send logs as soon as I get them

[Harvey021]

Can you please share the version of BSP you're working and the Steps and logs when problems occur?

Regards

Harvey

[djs2]

Sorry for the delay in replying.

We are using `linux-imx_5.15.71_2.2.2-phy5` from Phytec with patches from https://github.com/Freescale/linux-fslc/tree/5.15-2.2.x-imx up until 5.15.183.  Unfortunately the problem only occurs occasionally (less than 1 instance every 500 hours or so of CI testing across multiple units) and I haven't been able to create a simple reproducer.

An initial attempt to enable `CONFIG_CRYPTO_DEV_FSL_CAAM_DEBUG` prevents our device from booting as we are using the CAAM to encrypt the root filesystem along with various data partitions and this generates too much logging.

I'm looking at adding log information to a circular buffer and emitting this when the error occurs.  As this will only result in the last 1000 or so records being emitted, I'd like to know whether there are any setup messages that we should always log to support analysis.

Thanks

Daniel

[Harvey021]

Watchdog timeout error was triggered by DECO halt on but there were multi case to make DECO halt on, such as input/output buffer address, length or etc.
Can you reproduce this with stress test with "dd" or "fio" tool?

If the issue can be reproduced stably, it can help us to find the root cause.

Regards

Harvey