Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3472 - brcmfmac: can't handle firmware responses #8835

Closed
openwrt-bot opened this issue Nov 25, 2020 · 1 comment
Closed

FS#3472 - brcmfmac: can't handle firmware responses #8835

openwrt-bot opened this issue Nov 25, 2020 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

arinc9:

Device: ASUS RT-AC88U
OpenWrt: trunk as of 25th November 2020
Firmware: BCM43664/4 wl0: Nov 5 2018 03:19:56 version 10.28.2 (r769115) FWID 01-d2cbb8fd
Firmware: BCM43664/4 wl0: Jan 30 2019 17:31:05 version 10.10.122.303 (r666429 WLTEST) FWID 01-3569d737
Firmware: BCM43664/4 wl0: Aug 23 2016 17:19:51 version 10.10.69.69 (r625687) FWID 01-8438621f

brcmfmac can't seem to handle firmware responses. Here's the relevant path from the bootlog:

[ 11.280145] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM43664/4
[ 11.503465] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.asus,rt-ac88u.txt failed with error -2
[ 11.514615] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2
[ 13.870099] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 13.878396] ieee80211 phy0: brcmf_c_preinit_dcmds: Retrieving cur_etheraddr failed, -5
[ 13.886344] ieee80211 phy0: brcmf_bus_started: failed: -5
[ 13.891769] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-5
[ 16.350348] pci_bus 0001:01: 1-byte config write to 0001:01:00.0 offset 0x3c may corrupt adjacent RW1C bits
[ 16.360143] pci 0001:00:00.0: enabling device (0140 -> 0142)
[ 16.365816] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 16.375505] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 16.385188] brcmfmac 0001:01:00.0: enabling device (0140 -> 0142)
[ 16.391296] pci_bus 0001:01: 2-byte config write to 0001:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 16.400978] pci_bus 0001:01: 2-byte config write to 0001:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 16.580152] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM43664/4
[ 16.591812] brcmfmac 0001:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.asus,rt-ac88u.txt failed with error -2
[ 16.602960] brcmfmac 0001:01:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2
[ 16.713759] pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 16.952788] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM43664/4
[ 16.961624] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 16.972888] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43664/4 wl0: Nov 5 2018 03:19:56 version 10.28.2 (r769115) FWID 01-d2cbb8fd
[ 132.622766] ieee80211 phy1: brcmf_cfg80211_get_channel: chanspec failed (-52)

@openwrt-bot
Copy link
Author

arinc90:

This is the OP. I can't reach my account which this issue was opened from. This issue was caused by corrupt nvram and was fixed by simply resetting it. This issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant