RPI 3B+ Reboot Gets Stuck

[TimG]

If the CPU is still powered you can probably use the hardware watchdog to trigger a reboot automatically. See

https://www.freedesktop.org/software/sy ... conf.html#

and

https://github.com/raspberrypi/firmware ... ays/README

NB be sure to set the watchdog timeout to less than the maximum 15s allowed by the Pi’s watchdog timer (if this is in the official documentation I couldn’t find it).

[yzm157]

I am using a raspberry pi 4B without any peripherals connected，executing

Code: Select all

sudo reboot

will get stuck, the problem recurrence rate is 100%.
This problem began to appear when using a 64-bit system around August last year, upgrading to the latest bootloader also failed to solve the problem

[PiGuy512]

TimG, I did a few more tests and your idea to ground the pins helped me figure out that there is actually 2 problems that I'm experiencing. I have the Raspberry pi powered by a Raspberry pi power supply, the power supply is connected to my inverter as we have load shedding and I need the tests to run indefinitely. What I noticed by chance was that when load shedding happens, there is a small time(about 10 seconds) that the Raspberry pi has errors about being "under voltage" but this corrects itself and this doesn't happen again until another load shedding schedule.

I've connected the Raspberry pi to a lithium battery pack through a buck converter. This solved the problem with having to ground the PEN pin, I've run a few tests and the Raspberry pi only gets stuck between day 1 and day 2 and I always need to ground the RUN pin now.

Ill give the watch dog timer a try but will this still work in my situation?

On a side note, the logs still always end with "Restarting system".

[ganzgustav22]

Over a week later this test was still running without issue. The board had to be moved, but the test has been restarted.

OP of the https://github.com/raspberrypi/firmware/issues/1559 issue here.

Same or similar thing I noticed with the Pi4 two years ago:
https://github.com/raspberrypi/firmware ... -826749060

It would be really cool if you guys would fix that bug. Reboot being buggy is really annoying, there are people with Pis in hard to access remote locations.

[apricotfarm]

I am using a raspberry pi 4B without any peripherals connected，executing

Code: Select all

sudo reboot

will get stuck, the problem recurrence rate is 100%.
This problem began to appear when using a 64-bit system around August last year, upgrading to the latest bootloader also failed to solve the problem

EDIT: I'm having these troubles on a Pi 4, just to clarify

Exact same issue here. I'm finding this with a crispy-fresh Pi OS install with the "recommended" 32-bit version and also no peripherals connected. This happens on an older 1GB Rev. 1.1 board, as well as a 2GB Rev. 1.4 board. For me, the 64-bit OS install works fine, and the 32-bit "recommended' version sticks on reboot, every time. On both boards, I tried 2 diff official Pi 4 power supplies, and a 32 bit OS and a 64 bit OS install. The 32 bit version fails in all situations. Both boards have the latest firmware.

"sudo poweroff" works as expected.

Let me know if there is any additional information that I can supply that might help.

[apricotfarm]

Here's some additional information regarding my previous post. This applies to SSH only, running the Pi in headless mode. The reboot actually happens, but the SSH disconnect does not complete properly -- it just hangs there, even though the Pi is properly rebooting.

As far as I can tell, this ONLY happens when a wifi connect was present at boot time. When there's ethernet only, all is well. If I boot with ethernet only attached, then activate the wifi, all remains well. If I boot with both ethernet and wifi on, or just with wifi on, I have the issue.

I would love to see this fixed. I suppose it's arguable that the issue is of lesser importance since the remote Pi is actually rebooting, but it is extremely disconcerting to have the SSH connection hang whenever the remote Pi restarts.

[MyPie]

Hej folks,

came here to join the party, as I'm experiencing the same issues with my rPi 4 (2GB RAM, Debian).
Was anyone of you successful in the meantime?

Best,
MyPie