Le Potato fails to reboot when running headless

I'm running Raspbian 11 on Le Potato, and when I try to reboot, it often gets wedged in this state until I cycle the power:
    pi@exhale:~ $ sudo reboot
    Connection to 192.168.1.229 closed by remote host.
    Connection to 192.168.1.229 closed.
    ...
    $ ssh pi@192.168.1.229
    ssh: connect to host 192.168.1.229 port 22: Connection refused

With a serial console on 2J1, this is the final output:
    [  OK  ] Reached target Shutdown.
    [  OK  ] Reached target Final Step.
    [  OK  ] Finished Reboot.
    [  OK  ] Reached target Reboot.
    [   27.291648] watchdog: watchdog0: watchdog did not stop!
    [   27.324958] systemd-shutdown[1]: Syncing filesystems and block devices.
    [   27.327730] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
    [   27.343147] systemd-journald[287]: Received SIGTERM from PID 1 (systemd-shutdow).
    [   27.375125] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
    [   27.390846] systemd-shutdown[1]: Using hardware watchdog 'Meson GXBB Watchdog', version 0, device /dev/watchdog
    [   27.400543] systemd-shutdown[1]: Unmounting file systems.
    [   27.402985] systemd-shutdown[1]: All filesystems unmounted.
    [   27.407668] systemd-shutdown[1]: Deactivating swaps.
    [   27.412605] systemd-shutdown[1]: All swaps deactivated.
    [   27.417663] systemd-shutdown[1]: Detaching loop devices.
    [   27.425908] systemd-shutdown[1]: All loop devices detached.
    [   27.428478] systemd-shutdown[1]: Stopping MD devices.
    [   27.433768] systemd-shutdown[1]: All MD devices stopped.
    [   27.438808] systemd-shutdown[1]: Detaching DM devices.
    [   27.444797] systemd-shutdown[1]: All DM devices detached.
    [   27.449110] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
    [   27.464602] systemd-shutdown[1]: Syncing filesystems and block devices.
    [   27.467049] systemd-shutdown[1]: Rebooting.
    [   27.470940] kvm: exiting hardware virtualization

This only seems to happen when running headless (nothing connected to the HDMI port).  I can hack around the problem with a hard reboot:
    $ echo b | sudo tee /proc/sysrq-trigger

But that's no help when the system is already wedged.  Any ideas?

(I bought this thing because it's still available and fits the RPi3 case, but I can't seem to do anything without stepping on rakes.)
Sign In or Register to comment.