NicolasA Posted January 28, 2021 Posted January 28, 2021 Armbianmonitor: http://ix.io/2Nym Hi, I'm using a RockPi 4 B as a wifi access point. Everything is working fine with good performances until the Wifi stop working, usually after 3-4 days. When that happens, dmesg is flooded with these logs : [221057.075187] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221057.075202] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [221124.657840] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217786] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217806] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 Reloading `brcmfmac` module do not fix the issue, only a reboot. I'm using the latest firmware provided by armbian-firmare : # dmesg | grep brcm Jan 28 09:36:13 crumble kernel: [240969.028417] brcmfmac: F1 signature read @0x18000000=0x15294345 Jan 28 09:36:13 crumble kernel: [240969.038152] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 Jan 28 09:36:13 crumble kernel: [240969.041051] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.radxa,rockpi4b.txt failed with error -2 Jan 28 09:36:13 crumble kernel: [240969.042548] usbcore: registered new interface driver brcmfmac Jan 28 09:36:13 crumble kernel: [240969.149643] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 Jan 28 09:36:13 crumble kernel: [240969.149719] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available Jan 28 09:36:13 crumble kernel: [240969.149965] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Feb 11 2020 11:54:51 version 7.45.96.61 (be7af2d@shgit) (r745790) FWID 01-a41d86bd es7.c5.n4.a3 I'm not sure where to go from there. How can I debug or workaround this issue ? 0 Quote
NicolasA Posted January 28, 2021 Author Posted January 28, 2021 Hi, Thanks for your answer. No, who would that be ? The manufacturer or the kernel developer ? According to some rasberrypi forum, this type of errors could come from the firmware. I found a newer one (v 7.45.96.68) here : https://github.com/armbian/firmware/pull/19 I'll give it a try and keep you updated. 0 Quote
Salvador Liébana Posted February 2, 2021 Posted February 2, 2021 Hi guy's! anyone had experienced wifi desconections and very low wifi performance overall on mainline?? I have those on any of my rk3399s sadly. does anybody tried a workaround?? it's a really bad chip but on rpi4 it performs quite better (sadly). I also not experienced this kind of performance on previous kernels. 0 Quote
Werner Posted February 2, 2021 Posted February 2, 2021 4 hours ago, Salvador Liébana said: I have those on any of my rk3399s sadly I can only speak for the Pinebook Pro whiches WiFi runs stable for me on 5.10.y 0 Quote
NicolasA Posted February 2, 2021 Author Posted February 2, 2021 The issue is still here with the firmware v 7.45.96.68. Wifi crashed a little bit before reaching 5 days uptime. I will see if there is a way to reset the wifi chip, as a workaround. Unloading and reloading the module is not enough. @Werner Which firmware are you using with you Pinebook ? ( You can check it with `dmesg | grep brcmfmac`) 0 Quote
NicolasA Posted February 8, 2021 Author Posted February 8, 2021 So, I did test with multiple firmware revision : 7.45.96.0, 7.45.96.40-apsta, 7.45.96.53, 7.45.96.61, 7.45.96.68, 7.84.17.1 They all have the same behavior, except 7.45.96.0 and 7.45.96.40-apsta which crashes after only 1 day (instead of ~4 for the others); and 7.84.17.1 which create a very high CPU usage and is not usable. I found a workaround to reset the Wifi chip without rebooting : echo -n "fe310000.mmc" > /sys/bus/platform/drivers/dwmmc_rockchip/unbind sleep 1 echo -n "fe310000.mmc" > /sys/bus/platform/drivers/dwmmc_rockchip/bind It's working but not a real fix. It would be better to have a crash-free firmware. 0 Quote
NicolasA Posted February 18, 2021 Author Posted February 18, 2021 The above workaround does not work every time, once or twice and then you need to reboot. I got some debug logs from the driver, dmesg is flooded with this error : [85658.544429] brcmfmac: CONSOLE: 085641.821 wl0: PHYTX error [85660.512477] brcmfmac: CONSOLE: 085643.786 wl0: PHYTX error [85660.512502] brcmfmac: CONSOLE: 085643.788 wl0: PHYTX error [85662.404206] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [85664.964270] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [85664.964292] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [85668.900215] brcmfmac: CONSOLE: 085652.182 wl0: PHYTX error [85669.524228] brcmfmac: CONSOLE: 085652.795 wl0: PHYTX error Should we contact Raxda or Ampak for this issue ? 0 Quote
Tamino Posted March 24, 2022 Posted March 24, 2022 same Problem here, armbian 64 oa a Rock Pi 4B with an BCM4345/9 Chip... somone got it to work? 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.