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
This was referenced May 13, 2024
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 have the Zooz ZST10! A quick poke around HA and I found the firmware to be 2.3 but I can't find yet the SDK version on it... I'm hoping it isn't one that was flagged as being problematic for HA |
See below sites. Apparently you can update via HA now. I can't be sure about your firmware version though. But the HA site I mentioned earlier notes: "The SDK version does not have to match the firmware version. If you are unsure which SDK versions a firmware is based on, contact the manufacturer of your device." Also found below sites after a quick Google which might be helpful for your specific case. chrome_uRgy2A6IrN.mp4 |
This worked for me as well. Did a fresh install yesterday, no problems so far. GCFFlasher also is available in the AUR. For anyone not as comfortable on the CLI, here's what I did (the command is case sensitive):
|
|
Hello everyone, I think I'm encountering the same error but I can't find any solutions despite all your good ideas (thanks for sharing them by the way ;) ) Some useful info:
Installed on SD card
Installed on SSD on USB2
Given the problems encountered only on SSDs (once the Conbee2 version problem had been ruled out), I tasted the disk:
In brief:
If you have other leads to explore, I'd love to hear. |
|
2 cents: migrate away from your Pi 3(B+). The little RAM always was and still is an issue, I'd want to rule this out under any circumstances. When starting with HA I spent weeks troubleshooting instability issues, freezes and reboots, turned out: memory issues. pi 4 (with oversized 8 GB of memory) and never saw those exact issues again. /general sidenote |
|
Do we know if this was addressed or improved in 14.0? I don't see any movement on the upstream RaspberryPi/Linux issue. |
|
I think I will remain forever on 12.3 or at least till my ssd stops working 😅 |
That's what I'm worried about. I've been on 12.1 since March... |
|
I have the same problem with a Pi 4. After a fresh installation on a new sd-card the system worked without problems. I was also able to import the backup. A reboot via the cli works without any problems. I don't think it's related to the haos version but rather a bug in the way the addons are organized / started. All reboots had no effect on the system. In the end, however, I updated Whisper from 2.3.0 to 2.3.1. Since the update, the problem with the freezing system has reappeared. I have uninstalled the addon (core_whisper) via the CLI. After that, the system was stable. I then carried out the update to 2024.12.2. The system was still stable. I uninstalled the addon core_whisper via the CLI on the original (unstable) sd-card. After that, the system was stable. |
|
There may be something wrong with the Docker subsystem |
|
After updating the ConBee II firmware, my Pi3B+ again seems stable, running OS 14.1 now for a few hours when it used to reboot after a few seconds. Since deCONZ seems to admin that it's a bug in their device that requires a firmware update (changelog says "Fix loopbug behaviour caused by a USB stack bug."), I think this can be closed with a link to the details of #3362 (comment) or #3362 (comment) |
|
I can confirm, Pi3B+ here, I'm 100% new to HomeAssistant, fresh install from yesterday afternoon, it was stable all night. Rebooted this morning to perform tuning of the UCTRONICS PoE HAT fan, and things started to bootloop like described. Uding |
|
I hit the same issue after updating from HA OS 13.x to 14.1 today. I reported it here #3787 but then I found this issue. Updating the ConBee II firmware seems to have fixed it for me (already running for a few hours now). I wonder why it only started happening now, since the new firmware is from 2022. |
|
Updating the ConBee II firmware seems to have corrected the issue for me as well. Note, I needed to run the GCFFlasher command with root permission (Linux) to get it to work which I didn't find documented anywhere: |
|
Please leave the warning in the release log as long as this workaround is needed.
On a similar note, how to access the config.txt on the Pi5? |
|
And another host hiccup today:
The host was running for 113 days (since 2024-09-30) this time which is pretty awesome - but with Bluetooth integration set to passive mode since 2024-11-02. How (the freaking h**l) can we access host logs from prior the last boot (running HA OS)?!?
I want to figure out what is REALLY going on here. It is starting to be really freaking annoying.
|
|
I'm going to switch hardware (Pi 4 -> Pi 5). Is it expected the Pi 5 hardware also "needs" the |
|
Pi4 and 5 issues are unrelated to this issue as they run different kernel setups AFAIK. This issues relates to the 3B+ icw zwave and/or zigbee usb sticks. If you're having issues on a 4 or 5. A seperate issue should be created or found. Stop trying to hijack this thread with other issues. |
Migrated my main to Pi5 some time ago. Works out of the box and never skipped a beat. |
|
I just ran into this issue with a z-wave stick plugged into to USB on Pi3B. I also have a Rasbee plugged into the expansion slot on the Pi and this did not affect anything, it really seems related to the USB slot. The It also does not seem related to power consumption as I tried with different power adapters (some really too weak and some strong enough that both showed the same error as OP) and even different Pies just to be sure. |
|
I also been having this issue but did not correspond it with HA OS 12.3 upgrade. I reverted back to 12.2 (running core 2025.2.2) and its back to healthy. Any updates on this besides using Raspberry Pi 3b+ |
|
Same problem here for me. |
|
For these new reports, have you tried the steps in #3362 (comment) ? |
|
Yes I've tried to update my Sonoff dongle. |
|
I have a Pi 3B+ and I had the issue with the OS 13.2 and I added the parameter dtoverlay=dwc2 in config.txt and right now I am running OS 14.2 with the same Zigbee Conbee II without any problem.
As far as I know this problem is only related with Pi 3 |
|
In my case, ddtoverlay=dwc2 was already in config.txt |
|
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
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: