HA OS 15.1 + Raspberry Pi 3 (32-bit) + Aeotec Z-Wave usb stick = Boot loop

Installation Home Assistant OS
1

Hi,

After updating Home Assistant OS from 15 to 15.1 I get a boot loop if my Aeotec Z-Stick Z-Wave Gen5 USB stick (zw090-c) is plugged in.
Without it HA boots fine. But then if I plug it in and I enter the Z-Wave add-on configuration and submit it in Z-Wave JS add-on, HA prints the errors below and the Raspberry reboots.

raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-arm frequency: -110  
hwmon hwmon1: Failed to get throttled (-110)  
raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-arm frequency: -110  
mmc0: timeout waiting for hardware interrupt.  
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:  
rcu: 0(detected by 3, t=2102 jiffies, g=84341, q=94 ncpus=4)  
rcu: All QSes seen, last rcu_preempt kthread activity 2102 (42922-40820), jiffies_till_next_fqs=1, root ->qsmask 0x0  
rcu: rcu_preempt kthread timer wakeup didn't happen for 2101 jiffies! g84341 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200  
rcu: oPossible timer handling issue on cpu=0 timer-softirq=13553  
rcu: rcu_preempt kthread starved for 2102 jiffies! g84341 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0  
rcu: oUnless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.  
rcu: RCU grace-period kthread stack dump:  
rcu: Stack dump where RCU GP kthread last ran:  
mmc0: timeout waiting for hardware interrupt.

Downgrading to HA OS 15.0 didn’t help.
Also tried plugging it in using a powered USB hub.

2

Home Assistant OS 15.0 - no need to skip.

Probably need to use 64 bit version. Or think about upgrading from the pi 3.

3

Thank you for the link about 15.0.
Made me think about downgrading even further. 14.2 works!

4

That is not the correct course of action. Try applying the fixes in the linked topic.

1 Like
5

Sorry, which fixes do you mean? I only see the topic asking to update to 15.1.rc1, but for me 15.1 final was problematic.

6

That came out after the rc, and the fixes still apply.

image
image732Ă—176 5.34 KB

7

But I’m using Raspberry Pi 3 and no SATA or eMMC. Should I try fixes that don’t apply to my hardware?

8

No you need to:

9

Thanks, but for now I prefer my single command solution, which doesn’t require fresh OS install and migration or hardware upgrade.

10

It’s surprising that this happened for you only after the 15.0 to 15.1 update, as the Aeotec-based sticks have been causing issues for quite a while - but OTOH it makes sense the rollback didn’t help.

Unfortunately, it’s a kernel bug that’s been reported upstream but there was no traction on that because the sticks are not conforming to USB standards and are having more issues as well (e.g. the requirement to be plugged through a hub just to reliably enumerate). A fix is to use the non-default dwc2driver by adding dtoverlay=dwc2 to config.txt. We don’t want to do that by default but if the fixes your issues, you shouldn’t see any major performance or stability impact on your setup.

11

Thank you, that did the trick! Running 15.1 with no issues!