On Sun, 17 Oct 2021 13:10:19 -0400 Andres Salomon <dilinger@queued.net> wrote: > Package: firmware-brcm80211 > Version: 20210315-3 > Severity: normal > > This bug is mostly for documentation purposes. > > When running a raspberry pi 4b as an access point, after a random > period of time the on-chip firmware will crash and leave the wireless > driver (brcmfmac) unusable until the chip is reset. The rest of > the kernel is still fine, but the driver is unusable. > Here's the firmware version that's in Debian 11 (bullseye): > > [ 16.365079] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.clm_blob > [ 16.373443] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Sep 18 2020 02:27:58 version 7.45.221 (3a6d3a0 CY) FWID 01-bbd9282b > > Here's one example of the firmware crashing: > > Oct 12 17:40:06 wifi1 kernel: [263542.782712] brcmfmac: mmc_submit_one: CMD53 sg block write failed -84 > Oct 12 17:40:06 wifi1 kernel: [263542.785401] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame > Oct 12 17:40:52 wifi1 kernel: [263589.238359] brcmfmac: brcmf_sdio_hdparse: seq 77: max tx seq number error > Oct 12 17:40:54 wifi1 kernel: [263591.678597] brcmfmac: brcmf_sdio_hdparse: seq 240: max tx seq number error > Oct 12 17:40:54 wifi1 kernel: [263591.681542] brcmfmac: brcmf_sdio_hdparse: seq 241: max tx seq number error > Oct 12 17:40:54 wifi1 kernel: [263591.684591] brcmfmac: brcmf_sdio_hdparse: seq 242: max tx seq number error > Oct 12 17:40:54 wifi1 kernel: [263591.687778] brcmfmac: brcmf_sdio_hdparse: seq 252: max tx seq number error > Oct 12 17:40:54 wifi1 kernel: [263591.690801] brcmfmac: brcmf_sdio_hdparse: seq 253: max tx seq number error > Oct 12 17:40:54 wifi1 kernel: [263591.693780] brcmfmac: brcmf_sdio_hdparse: seq 254: max tx seq number error > Oct 12 17:41:36 wifi1 kernel: [263633.105406] brcmfmac: brcmf_sdio_hdparse: seq 171: max tx seq number error > Oct 12 17:50:57 wifi1 kernel: [264194.196126] brcmfmac: mmc_submit_one: CMD53 sg block write failed -84 > Oct 12 17:50:57 wifi1 kernel: [264194.199127] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame > Oct 12 17:52:12 wifi1 kernel: [264268.874931] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 > Oct 12 17:52:14 wifi1 kernel: [264271.434963] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 > Oct 12 17:52:14 wifi1 kernel: [264271.438681] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 > > I'm currently trying a newer Cypress firmware (from unstable), so > we'll see if it also has the same crash. Yesterday on #debian-raspberrypi we had a user running a RPi 3B (not 3B+, so no 5 Ghz band (thx steev!)) using it as an AP, reporting something similar/same: > My pi (or maybe just the wifi) crashes every day/ every couple of days with > this in the logs shortly before: > "ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110" I was waiting on a (potential) bug report to document the findings, then Andres mentioned this bug report, so I'll log it here. The first thing I found was: https://lore.kernel.org/all/fcf95129-cba7-817d-4bfd-8efaf92f957f@gmail.com/ which seems to indicate it's primary a firmware issue (firmware-brcm80211), but I've found out that there is also a change in the kernel code block related to this. I'm not 100% sure as it was a quick scan, but I found this commit: https://github.com/torvalds/linux/commit/78f0a64f66d4f582987bbe45433374b61c21500f This code is present in 5.14, but not in 5.10. Andres: You mentioned bullseye in your initial report, but it didn't have the usual footer mentioning various program versions and I'm especially interested in the kernel version. Could you mention that in subsequent reports (if any)? The user in #debian-raspberrypi was using kernel 5.10.0-9-arm64 on a Bullseye system. I then suggested to try the firmware-brcm80211 from testing to see whether that would make a difference. I'll leave the progress reporting up to the users themselves. Cheers, Diederik
Attachment:
signature.asc
Description: This is a digitally signed message part.