HAOS brcmfmac errors + reboot

For the past couple of HAOS versions, my Raspberry Pi 3B+ (Core: 2024.5.5, Supervisor: 2024.05.1, Operating System: 12.3, Frontend: 20240501.1) is emitting the following to the console (the following are just the latest…):

2024-06-02 05:19:20.473 homeassistant kernel: brcmfmac: brcmf_sdio_read_control: read 2048 control bytes failed: -5
2024-06-02 05:19:20.497 homeassistant kernel: brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
2024-06-02 05:43:20.611 homeassistant kernel: brcmfmac: brcmf_sdio_read_control: read 2048 control bytes failed: -5
2024-06-02 05:43:20.612 homeassistant kernel: brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK

and:

2024-06-02 01:49:59.253 homeassistant kernel: mmc1: Got command interrupt 0x00000001 even though no command operation was in progress.
2024-06-02 05:19:20.128 homeassistant kernel: mmc1: Controller never released inhibit bit(s).
2024-06-02 05:43:20.356 homeassistant kernel: mmc1: Controller never released inhibit bit(s).

and:

2024-06-02 10:24:24.071 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -16
2024-06-02 14:22:16.384 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -16
2024-06-02 14:58:34.584 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -16
2024-06-02 15:18:46.840 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -16

It will eventually reboot within a day or so, but certian addons may become unresponsive before that.

Nothing has changed with my configuration, which has been working flawlessly for ~3 years now - but the occasional HAOS update.

I’ve setup abother Pi (RPi5) - but as soon as HAOS boots, the same error appears… (I’ve seen none from the Raspberry Pi OS installed…)

Is this a known issue? Anyone else has encountered it?

Thanks!
dd.

1 Like

I have the same issue, I formatted the sd 4 times with and without restoring the backup and I always get this error after a while, which will restart the system.

I have the same issue since last two upgrades. I also lose most Mqtt. wont accept connections.

Yes, I am also suffering from brcmfmac errors all of a sudden. My config has not changed in ages, other than upgrading HA. I thought my SD card might be dying so tried a brand new one and also tried moving to SSD with a Pi 5 HAT, but still get brcmfmac errors when I try a fresh install and a restore from backup.

Something fishy going on in HA?

Went away by 2014.7 .

On my Pi3+ board this issue hangs it up also on HA Core 2024.7.1 so lucky You @Entryway7625
Maybe this ‘brcmfmac’ is something related to a configuration when SSD instead SD card is in use (like me too) but otherwise @iand69 encounters it also on SD right ?
Thanks in advance for any suggestions.

Same problem here and it is persistent.
Exchanged the RPi 3B+ for a new board but no change.

In my case error messages come in this combination

mmc1: Controller never released inhibit bit(s).
brcmfmac: brcmf_sdio_read control: read 1536 control bytes failed: -5
brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
mmc1: Got command interrupt 0x00000001 even though no conmand operation was in progress.
mnc1: Got command interrupt 0x00000001 even though no command operation was in progress.

The last message repeats until the systems becomes unresponsive.

https://forums.raspberrypi.com/viewtopic.php?t=330384 suggests that this error is specific to 64-bit on a 3B+ and suggests to change EEPROM settings but I have not idea how to do it on HAOS.

Any suggestions?

almost the same. The rasp Pi get slow or unrepsonsive, and suddenly reboots.

this is spammed on screen:

[ 3942.681080] brcmfmac: brcmf_sdio_read_control: read 1536 control bytes failed: -5
[ 3942.681197] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
[ 4910.532576] mmc1: Controller never released inhibit bit(s).

EEPROM settings are persistent and independent of OS. So boot with Raspberry OS, change EEPROM settings, reboot with HAOS

Had to reboot RP4-64 today and experiencing the same issue:
CIFS: UFS: Error connecting to socket. Aborting operation
CIFS: UFS: cifs_mount failed w/return code = -115
brcmfmac: brcmf_set_channel: set chanspec 0xnnnn (now d02e increasing) fail, reason -52

Updated every time all sw .
tototaly don’t know what it means or where it comes from and how to solve this!

Help?!

Hello

I have same problem, I started my adventure w HA month ago and I cant use it propeply, there is crushing a lot of day during day, it’s not stable, I dont have eprom in rpi 3b +. When I was week away from house then problem was solved for while but when came its return.

Any help?

I have this exact same set of error messages with my Pi3B+ and EEPROM is only relevant for Pi4 onwards.

It’s been very unstable and I haven’t found a solution. I can almost guarantee a hard lock up where HDMI will just go black and completely unresponsive, by trying to update HAOS (currently on 2024.7.2)

Currently looking at putting an old school timer under the power supply to force a power cycle during the night, whilst looking at moving it to different hardware/ finding a concrete solution.

HomeAssist kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
I am receiving the above error in my HOST log.
I am running on a raspberry Pi 4. Getting about 5 error loggings per second.
Does any one have a suggestion on how to eliminate these errors?
Thank you

Regarding this repeating message in CLI (with 0x#### variations), which had been multiplying from 6 items once on startup to now dozens repeating every few minutes over recent weeks. This seems to be an unanswered question on these forums, so this is my solution.

brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52

I found on the Raspberry Pi Forum some guidance about Broadcom WiFi chipset errors, with some varying advice about setting country restrictions on the WiFi channels available in your region, etc. However, the way I actually solved it was by disconnecting the WiFi (from Home Assistant UI network settings, while connected via Ethernet), turning off IPv6, and re-selecting the appropriate SSID, entering the password and gateway/DNS again.

No more messages have shown up since, even after a restart. Yay! Hope this helps.