poweroff/shutdown on a Pi 400 can stall
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c, linux
- Domain
- embedded-iot, operating-systems
Research direction
Start by reviewing commit 63bd88ba88650a34ba10006aa2722b1f699e34ad and the mailbox GET/SET path described in the report. Reproduce the intermittent Pi 400 shutdown stall, then verify that poweroff completes reliably without leaving the display active.
Written by the indexing model from the issue text.
Description
The most recent firmware release (https://github.com/raspberrypi/firmware/commit/0c3ecac52e4ef4dde82e6261b917fd77a884be37) prevents Pi 400 from powering off reliably - there's at least a 50% chance that it will stall with the display still active. Pi 400 bypasses the usual watchdog-based poweroff mechanism and uses one of the GPIOs on the expander to trigger a full power down. Control of the expander is via mailbox calls, and in the failure case the first of two mailbox methods (the GET from the GET/SET pair) appears not to be completing.
Although suspicion first fell on the recent tryboot changes, either in the firmware or in the kernel, these appear not to be the cause. sudo SKIP_KERNEL=1 rpi-update exonerated the firmware changes, and choosing a few strategic commits to test turned my attention to the 408 upstream commits. A few hours of bisecting later (which took two attempts due to the probabilistic nature of the failure) pointed the finger of suspicion at 63bd88ba88650a34ba10006aa2722b1f699e34ad - which makes sense as it is a mailbox-related change.
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·
-
bug Self Built Image SNAPSHOT Supported Device target/ramips
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100