Debugging SError

[sfalsig]

@Bibek

I would rather suggest to check the Address which has caused the error. Mostly, unprivileged/unmapped address or unpowered/unclocked registers.
Please attach the complete log.

Thanks! Where do I find the address? I’ve attached a full dmesg log (dmesg.log (65.6 KB)). Even though I get a BUG and some backtraces, that to me seems to be because the SError handler triggers some functions to be run from an unsupported context that those specific cores just happen to be in?
Also, for reference, the exact same code is running without these issues on a lot of other boards though, so I suspect this to be a hardware issue. Any hint on which part of the TX2 is causing these errors would be very useful.

@sumitg

• ESR, bit [25] is: IL - Instruction Length for synchronous exceptions and not “Implementation Defined”.
• “ISS encoding for an SError interrupt” bit [24] is: IDS - IMPLEMENTATIONDEFINED

Ah yes, of course - I meant bit [24].

@sumitg

You will get more debug info from implementation-defined registers in kernel logs after the SError prints.

Not sure I’m seeing that though? See comment above.