0

Reboot fails, cold start works

Al_

January 12, 2023 18:28

None

Follow

Hi

Consistently, my headless RPi3 + AMP2 + Raspberry OS kernel 5.4.79-v7+ fails to work after reboot, but reliably starts after disconnecting and reconnecting to power. My other 4 RPi (without AMP) reboot flawlessly. Basic software is similar on all (ansible managed; albeit details vary). It is not just the WiFi that fails: the RPi has an infrared receiver connected directly to the GPIO and that one does also not work after reboot. So the RPi seems to be totally dead in that moment.

As the workaround is to power off and on, I was wondering whether the fact that the AMP provides the power supply to the RPi is related to the issue. Anyone has seen the same behaviour?

Al_

 

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Al_ January 13, 2023 07:38

  Additional information: I retrieved dmesg of the latest reboot (that had failed, i.e., the soft reboot prior to the current cold boot). The last dmesg line in the failed reboot is from HifiBerry:

  snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok

  This may make it even more suspicious that failing to soft reboot is linked to the HifiBerry Amp. Even so the line is a success, no warning/error.

• 0
  
  HiFiBerry team January 13, 2023 08:59

  That's a normal message telling you that the driver has been mapped to the I2S stack. That's just as it should be.

• 0
  
  Al_ January 14, 2023 17:06

  Yes, it is normal: no warning, no error, as I wrote in my comment.

  Still, it makes me suspicious that the last dmesg message prior to failure comes from the HifiBerry Amp; which is a hardware piece different from all my other RPis, and which is the power source for the RPi (and power off is the difference between successful cold boots and soft reboots).