Hello,
i am on linux-imx 5.4.70_2.3.0, on a custom imx8qxp based board
Only on certain reboots, generally, soft reboot, i get this message:;
imx-scu scu: RPC send msg timeout
as
[ 4.069200] 003: imx-scu scu: RPC send msg timeout
[ 4.069227] 003: imx-secvio-sc scu:secvio: Fail read secvio config -110
[ 4.069235] 003: imx-secvio-sc scu:secvio: Cannot read secvio status: -110
[ 7.141193] 003: imx-scu scu: RPC send msg timeout
[ 7.141214] 003: imx-secvio-sc scu:secvio: Fail read secvio config -110
[ 7.141221] 003: imx-secvio-sc scu:secvio: Cannot read tamper 1 status: -110
[ 7.142033] 003: imx-secvio-sc scu:secvio: Failed to get secvio state
in such cases, i then get a constant error over time
[ 62.431240] 000: imx-scu scu: RPC send msg timeout
[ 154.335251] 000: imx-scu scu: RPC send msg timeout
[ 173.535245] 003: imx-scu scu: RPC send msg timeout
[ 186.847241] 002: imx-scu scu: RPC send msg timeout
[ 194.015239] 003: imx-scu scu: RPC send msg timeout
[ 211.167244] 003: imx-scu scu: RPC send msg timeout
[ 218.335253] 000: imx-scu scu: RPC send msg timeout
[ 239.583252] 000: imx-scu scu: RPC send msg timeout
[ 244.703251] 000: imx-scu scu: RPC send msg timeout
[ 265.951252] 002: imx-scu scu: RPC send msg timeout
Any hint is welcome
regards
angelo
Hello,
The error printed in kernel log shows that the message sc_seco_secvio_config sent by SCU to SECO callback failed.
Could you share a bit more information, like how easy is this to reproduce?
Have you tried to reproduce this on a MEK board?
Best regards,
Aldo.