balena-raspberrypi
balena-raspberrypi copied to clipboard
systemd-shutdown: adjust watchdog expiration time
By default, the second stage watchdog time that is used to set the watchdog once systemd-shutdown has stopped all services and replaced PID1 with itself is set to 10m.
However, the RPI watchdog has a maximum timeout of 15s, so we adjust this value accordingly.
This helps ensure that when a shutdown or reboot is triggered, the device can fallback to a watchdog reboot if it gets stuck.
Changelog-entry: adjust reboot watchdog timeout
Passed tests:
- test-raspberrypi — OS tests have passed
- test-raspberrypi2 — OS tests have passed
- test-raspberrypi3 — OS tests have passed
- test-raspberrypi3-64 — OS tests have passed
- test-raspberrypi4-unipi-neuron — OS tests have passed
- test-revpi-connect — OS tests have passed
- test-rt-rpi-300 — OS tests have passed
- test-raspberrypi0-2w-64
- test-raspberrypi4-64
@resin-jenkins retest this please
TODO: check the configuration is correctly set after solving conflicts
@resin-jenkins retest this please
@resin-jenkins retest this please
@resin-jenkins retest this please
Verified the settings on the raspberrypi4-64 docker image.
@resin-jenkins retest this please
@resin-jenkins retest this please
@resin-jenkins retest this please
lgtm
@resin-jenkins retest this please
Passed:
- test-raspberrypi3
- test-raspberrypi3-64
- test-raspberrypi4-64
Passed:
- test-raspberrypi0-2w-64
- test-raspberrypi3
- test-raspberrypi3-64
- test-raspberrypi4-64
@resin-jenkins retest this please
@resin-jenkins retest this please
@resin-jenkins retest this please
@resin-jenkins retest this please