We’ve checked with developer that watchdog not work due to status disabled in device tree. I’ve also verified that watchdog would work after enabling it on the devkit.
If you don’t want to modify anything at your side, why you ask the question here and so many questions…
Hey, you guys are the ones telling us which features are supported in 5.1
If you tell it works but disable the feature in the device tree then this is called a bug.
Fix it, we bought your hardware, we expect working software.
Quote from Update and Redundancy — Jetson Linux Developer Guide documentation The slot that the running system booted from is called the **current slot**. The other slot is called the **unused slot**. The system exchanges the roles of the current and unused slot in the course of an update, or when the software fails repeatedly during or immediately after a boot.
After 5.0.2 I thought the software could not become any worse…
Besides, are you really telling me that you could not find out with a test that A/B failover is not working in 5.1 for 2 weeks, but on the other hand you’re able to test your fix within 28 minutes?
I think solving the watchdog problem alone wouldn’t have solved the whole issue from the beginning, not? because the purpose of the watchdog is to restart the system after the kernel panic and we can actually do that manually by pressing the restart button without a watchdog, which will trigger the system to go into this restarting endless loop. I can confirm that this endless loop problem is happening also on my side.
Thanks for the important information about the disabled watchdog. Now I can understand why didn’t the system restart automatically after the kernel panic, but unfortunately it didn’t switch to the backup rootfs partition and went into an endless loop.