[Image lifted from one of the reference links below].
The Pi has manifested this issue for some time, but as I'm the only one likely to ever encounter it, I've had it low on the TODO list.
Previuous investigations have revealed the cause: that by using gpio-poweroff in the setup.sh script (as part of the handshaking between Pi and Arduino) I've broken the normal shutdown process.
#Set GPIO27 to follow the running state: it's High while running and 0 when shutdown is complete. The Arduino will monitor this pin.
dtoverlay=gpio-poweroff,gpiopin=27,active_low
References:
https://forums.raspberrypi.com/viewtopic.php?t=143519
https://raspberrypi.stackexchange.com/questions/127947/pi-zero-doesnt-fully-shut-down-after-adding-a-gpio-poweroff-dtoverlay-to-boot
Yup, this is me:
"Use of this overlay (and the gpio-poweroff mechanism) required that there is an external mechanism to remove the power in response to the GPIO being toggled. Failure to do so within the allowed window (3 seconds is the default) results in a kernel warning, followed by undefined behaviour."
Today I've encountered the same kernel panic in another Pi-based project, and I commenced some fresh investigation into the issue, which has unearthed this apparent gem:
"Some approaches for a constant status led (ab)use the gpio-poweroff overlay which interrupts proper shutdown procedures, but gpio-led doesn’t."
So I'm experimenting with this as a replacement line:
dtoverlay=gpio-led,gpio=27,trigger=default-on,active_low
It won't be in 'vNext' (4.5.1) as I want to let it soak for QUITE a while in Dev before I let it loose on you.
More references:
https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README
- Greig.
[Image lifted from one of the reference links below].
The Pi has manifested this issue for some time, but as I'm the only one likely to ever encounter it, I've had it low on the TODO list.
Previuous investigations have revealed the cause: that by using
gpio-poweroffin the setup.sh script (as part of the handshaking between Pi and Arduino) I've broken the normal shutdown process.#Set GPIO27 to follow the running state: it's High while running and 0 when shutdown is complete. The Arduino will monitor this pin. dtoverlay=gpio-poweroff,gpiopin=27,active_lowReferences:
https://forums.raspberrypi.com/viewtopic.php?t=143519
https://raspberrypi.stackexchange.com/questions/127947/pi-zero-doesnt-fully-shut-down-after-adding-a-gpio-poweroff-dtoverlay-to-boot
Yup, this is me:
Today I've encountered the same kernel panic in another Pi-based project, and I commenced some fresh investigation into the issue, which has unearthed this apparent gem:
So I'm experimenting with this as a replacement line:
dtoverlay=gpio-led,gpio=27,trigger=default-on,active_lowIt won't be in 'vNext' (4.5.1) as I want to let it soak for QUITE a while in Dev before I let it loose on you.
More references:
https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README
- Greig.