Bug 211731 - Wifi (brcmfmac) regression between 20201218 and 20210208 on Raspberry Pi 4
Summary: Wifi (brcmfmac) regression between 20201218 and 20210208 on Raspberry Pi 4
Status: REOPENED
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: ARM Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-13 13:05 UTC by Ruud
Modified: 2021-02-21 13:02 UTC (History)
3 users (show)

See Also:
Kernel Version: 5.10.14
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
Kernel logs for failed boot and good boot (5.54 KB, text/plain)
2021-02-13 13:05 UTC, Ruud
Details

Description Ruud 2021-02-13 13:05:30 UTC
Created attachment 295257 [details]
Kernel logs for failed boot and good boot

After upgrading the linux-firmware package (https://archlinuxarm.org/packages/armv8/linux-firmware) from 20201218.646f159 to 20210208.b79d239, my wlan0 interface no longer showed up in networkctl, and dmesg shows errors including

    brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

After downgrading to 20201218, everything worked fine again. This is on a Raspberry Pi model 4. I can reproduce both with kernel 5.4.83 and with kernel 5.10.14 from the Arch Linux ARM package (https://archlinuxarm.org/packages/aarch64/linux-raspberrypi4).

I can reproduce consistently, let me know if there is anything I can do to help.
Comment 1 Ruud 2021-02-14 08:05:36 UTC
I reported this to https://github.com/raspberrypi/linux/issues/4145 instead.
Comment 2 hexchain 2021-02-15 14:36:35 UTC
It seems that this also happens with the vanilla kernel (linux-aarch64 on ALARM).

Looking at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/brcm?id=870b805dc77e3f7acb7e6c36944936e310be2478, manually reverting the "boardflags3" change in brcmfmac43455-sdio.raspberrypi,4-model-b.txt seems to fix the problem. In other words, change that line back to:

> boardflags3=0x44200100

fixes the issue for me.

Can we please reopen this?

Note You need to log in before you can comment on or make changes to this bug.