Hi All - wondering if anyone can shed any light on this.
Running the latest Ubuntu Core image on Raspberry Pi CM4 hardware.
Triggering a reboot with the following command, but it seems to be resulting in a full hardware shutdown, rather than reboot (assuming that, because the system doesn’t recover from the reboot - but the activity LED is flashing when it’s in this semi-shutdown state):
dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 “org.freedesktop.login1.Manager.Reboot” boolean:true
This is up there with the most serious issues a headless / remote device could have, because it will require a site visit to resolve.
Would appreciate any insight / additional testing that could be done to figure this out.
The hardware watchdog is enabled on the CM4.