Hi David. Yes, those are the exact operations taken. We observe this after 3 reboots, as shown in the log attached.
1.0_RECOVERY_MODE_TESTING_DEFAULT_IMAGE.log (308.1 KB)
No kernel panic occurs and I can not see any obvious error in the logs.
The issue seen here runs successfully within 10 seconds of systemd starting up. We’re now testing if this issue occurs if we reboot after the nv-l4t-bootloader-config service succeeds.
Our assumption is that rebooting too quickly means this service never gets to set a UEFI variable, causing the system to believe it has not booted successfully.