Raspberry Pi bootloop after 12.3 update (usb related) #3362
Labels
Comments
|
Same issue with Raspberry Pi 3, 32-bit, with Zooz ZST10 usb dongle. |
|
I tried reproducing the issue here but I might be still missing something that's triggering the issue, so I'd like to gather following information about your setups:
Also, the following logs from some of you will be very useful:
|
sairon
changed the title
For me it's as follows:
As far as pattern goes. It all seems to be USB protocol controllers that are having issues. For me it's a Zwave usb controller, I think I saw zigbee controller usb as well. -EDIT- It's not my strongsuit, so couldn't get dmesg info. Is there a way to kinda freeze the system to stop everything else but CLI commands? Anyway, did manage to get the failed boot log, see below. |
|
Closed accidentally |
|
Here:
|
dmesg logha host logs logPhoto of HDMI output
|
|
The following also crashes the system:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@playaz44 This issue tracks booting problems in Raspberry Pi platform only. VM installations are running a different kernel version, please create a separate issue for that. Also, please check the host console when the issue occurs, something should be (hopefully) printed there. |
Similar issues in downgrading back to 12.2 as #3352 (comment) and #3352 (comment) |
|
I have found raspberrypi/linux#6100 that reported highly similar issue with 6.6 kernel a while ago, claiming 6.6.29 (which isn't in the stable branch yet) fixed the issue, so checking if it's the case for us might be worth a try as well. Here's a custom dev build with the latest RPi Linux from the master branch: If there's anyone who could give it a try (i.e. install it on an SD card and follow the same steps that lead to the boot loop with fresh 12.3), it would be much appreciated 🙏 Please note you need to be logged in on Github in order to download the artifacts, and that all the images are wrapped in an extra .zip archive, so you must first unpack that before you follow the standard flashing procedure. |
The 32-bit image resulted in the same crash unfortunately. |
I tried the rpi3-64 image, and got the same result. dmesg output |
|
@mvdnes Thank you very much. Can you try adding |
Tested with the image from above, by only changing the cmdline parameters. Unfortunately, it still crashes for both of the options. |
|
@mvdnes Thank you, I finally managed to reproduce it reliably here too - starting Z-Wave add-on with Z-Wave.me UZB stick seems to crash it every time. I am not able to reproduce it with any of the Zigbee sticks I have here, even if I set up a simple testing network. It is also reproducible on RPi OS with the I will report this issue to the RPi kernel repo, but I want to make sure we're not chasing ghosts and the cause is the same. Can you retry (hopefully for the last time) and make sure the parameters are properly set? In Just disabling the FSM is not sufficient. Alternatively, adding |
|
I have added the dmesg log of dwc_otg.fiq...=0However, the config.txt line with dmesg log of dtoverlay=dwc2 |
|
I can reproduce a system freeze incl. reboot as mentioned in raspberrypi/linux#6172. This is a fresh install. Inserting a ConBee II into a USB slot, autodiscovery works. The system freezes right when I try to configure the ZHA integration via GUI and can't be reached via network. Comes back up after. Just did it. logs before configuring ZHACoreHostlogs after configuring ZHACoreHostIf I can help troubleshooting, I will be happy to do so. System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
|
rpi 3 v1.2
full system info is on the linked issue I created. |
|
Similar issue (imo same, just wrongly described as bootloop) here with Raspberry Pi 3B+ and Conbee II USB Zigbee dongle. Was working up until 12.2. with Zigbee integration. Updating to 12.3 causes:
Downgrading to 12.2 fixes it. |
|
@That-one-Joe Interesting, that is slightly different from what I see with the Z-Wave stick - there the system cannot recover when I just remove the USB stick (unless watchdog kicks in and reboots the device - are you sure it's not the case? You should be able to figure it out from the system uptime). Also I wonder if this issue is also resolved by adding |
I thought of a freeze at first too. But after connecting the pi to a monitor, the CLI clearly showed bootloop behavior. And if it was actually frozen, nothing would happen if I would disconnect the Z stick. But as it is not frozen but bootlooping, the first time it boots after the Z stick is disconnected it boots all the way (without the zwave functionality of course). If this is not the case for you, I'd advise creating a seperate issue. |
|
I can't comment without closing the issue for some reason. So re-opened again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
After upgrading to 12.3 my HA started bootlooping. Noticed that after I disconnected my Aeotec Z-Stick ZW090 it booted again and ran fine (without my Z wave network of course).
What operating system image do you use?
rpi3-64 (Raspberry Pi 3 64-bit OS)
What version of Home Assistant Operating System is installed?
12.3
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: