Numerous kernal errors in log

1

While looking in the log for another issue, I noticed this error is occurring almost every second:

kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52

Any idea what is causing this error and/or how to fix it?

2

That’s the Broadcom wireless driver. I see errors from it every few hours on RPi 3B+. I’m not sure why you’re at 1/sec unless there’s something quite upsetting to the wireless link.

Broadcom firmware is proprietary…that’s the best I can answer “how to fix?”. So check config, etc. or try reinstalling the driver.

https://wiki.debian.org/brcmfmac

3

Interesting… I’m using a RPi 4 connected via Ethernet so never setup the WiFi. I need to check my HamVoIP node to see if it has the same error.

4

You can disable/enable wireless using sudo rfkill toggle wlan and see if that quiets things down.
EDIT: If necessary, install rfkill with sudo apt install util-linux

5

That can mean a number of things from WiFi signal interference to your WiFi chip is dying. If you aren’t using WiFi, try turning it off completely and see if that silences the error.

6

I looked at one of my ASL3 nodes that doesn’t use WiFi, and i have the same thing upon setting the WiFI country but setup no configuration:

[188456.466202] brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
[188456.570186] brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
[188456.674204] brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
[188551.354441] brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
[188551.462432] brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
[188551.566431] brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
[188551.670432] brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52

I added the following at the end of /boot/firmware/config.txt to completely disable the WiFi chip:

[all]
dtoverlay=disable-wifi
2 Likes
8

I recreated it by logging in from console and ifconfigging wlan0 down, then up - even with a configured wifi network and a configured country, it generates the errors until the connection sets up.