WiFi Instability Pi 3B+

[adamvb]

Hello!

I've recently got a Pi3B+ for a project I'm doing and due to the location requirements, I've had to have it on WiFi and not Ethernet.

I've been having issues with the Pi dissappearing off the network within a few hours of booting. The Pi is always active still, but the WiFi link dies until the Pi is rebooted. It appears there is a firmware trap issue in the log files, but despite initially using raspbian-2019-04-09 to start with and then raspbian-2019-06-24 and raspbian-2019-07-12 since, I've still not been able to get a prolonged connection.

In dmesg I see intermittant messages of:

Code: Select all

brcmfmac: brcmf_run_escan: error (-52)
brcmfmac: brcmf_cfg80211_scan: scan error (-52)

And then when the WiFi adaptor actually stops working:

Code: Select all

Aug 24 00:56:34 pisprog kernel: [20416.226897] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
Aug 24 00:56:37 pisprog kernel: [20418.645850] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 24 00:56:37 pisprog kernel: [20418.646268] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Aug 24 00:56:37 pisprog kernel: [20418.646286] brcmfmac: brcmf_run_escan: error (-110)
Aug 24 00:56:37 pisprog kernel: [20418.646296] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Aug 24 00:57:37 pisprog kernel: [20478.645431] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 24 00:57:37 pisprog kernel: [20478.645870] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Aug 24 00:57:37 pisprog kernel: [20478.645890] brcmfmac: brcmf_run_escan: error (-110)

Where the Pi is located, the stats in iwconfig seem pretty good, although I do see around 50 Tx excessive retries over a 6 hour period - output below:

Code: Select all

pi@pisprog:~ $ iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:"AdsNet"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 0C:80:63:F7:07:78   
          Bit Rate=72 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=51/70  Signal level=-60 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:27  Invalid misc:0   Missed beacon:0

I've made sure that GB - UK is set for my wireless country code, and I've checked in dmesg that power management for the adaptor is off.

I'm at a loss of what to try next - can any of you kind people offer any advice/anything else I can try?

[adamvb]

Just to add - this is the information for the adaptor from dmesg:

Code: Select all

pi@pisprog:~ $ dmesg | grep brcmfmac
[    5.388287] brcmfmac: F1 signature read @0x18000000=0x15264345
[    5.400933] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.401784] usbcore: registered new interface driver brcmfmac
[    5.632513] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.652276] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    8.433719] brcmfmac: power management disabled

[bme]

I am seeing the same thing on one of two new Pi 4's (1 GB is showing this issue, 4 GB is not), and I am looking for some help in what to do.

What I see in syslog when the problem appears to start is:

Sep 8 13:37:54 frozone kernel: [15252.534289] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
Sep 8 13:37:57 frozone kernel: [15254.947156] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 8 13:37:57 frozone kernel: [15254.947606] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 8 13:37:57 frozone kernel: [15254.947622] brcmfmac: brcmf_run_escan: error (-110)
Sep 8 13:37:57 frozone kernel: [15254.947636] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Sep 8 13:37:59 frozone kernel: [15257.507193] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 8 13:37:59 frozone kernel: [15257.507639] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 8 13:38:02 frozone kernel: [15260.067257] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 8 13:38:02 frozone kernel: [15260.067706] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 8 13:38:02 frozone kernel: [15260.067723] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110

Then, after a little while this is what I get repeating ad nauseum:

Sep 8 13:39:42 frozone kernel: [15360.389783] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Sep 8 13:39:45 frozone kernel: [15362.949390] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Sep 8 13:39:47 frozone kernel: [15365.509430] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
...three lines repeated until power cycled to reboot.

Checking the firmware returns the following:

apt-cache policy firmware-brcm80211
firmware-brcm80211:
Installed: 1:20190114-1+rpt2
Candidate: 1:20190114-1+rpt2
Version table:
*** 1:20190114-1+rpt2 500
500 http://archive.raspberrypi.org/debian buster/main armhf Packages
100 /var/lib/dpkg/status
20190114-2 500
500 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Packages

The first time this occurred, it took a number of days to appear. It appears to be increasing in frequency unfortunately. I re-installed Raspian last night in the hopes that I had munged something while tinkering, but the system dropped off the network about 4 hours later.

I am new to these systems. What should I do next to try to resolve this? Is there a chance this is actually a hardware issue?

Thanks!

[BenQ204]

Hey Adam - are you using the internal wifi adapter or do you have a separate USB adapter plugged in?

[mgssnr]

Hi, I just would like to add a bit of data to this conversation.

This occurred to me today on my RPi4 4GB model, using the internal WiFi on the RPi4:

Sep 27 10:19:01 localhost kernel: [158369.221537] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
Sep 27 10:19:20 localhost kernel: [158388.214273] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:20 localhost kernel: [158388.214759] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:23 localhost kernel: [158390.774325] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:23 localhost kernel: [158390.774778] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:23 localhost kernel: [158390.774792] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Sep 27 10:19:32 localhost kernel: [158400.054477] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:32 localhost kernel: [158400.054997] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:34 localhost kernel: [158402.614551] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:34 localhost kernel: [158402.615021] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:34 localhost kernel: [158402.615036] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Sep 27 10:19:37 localhost kernel: [158405.174580] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:37 localhost kernel: [158405.175055] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:40 localhost kernel: [158407.734633] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:40 localhost kernel: [158407.735060] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:40 localhost kernel: [158407.735075] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Sep 27 10:19:42 localhost kernel: [158410.294678] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:42 localhost kernel: [158410.295123] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:45 localhost kernel: [158412.854752] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:19:45 localhost kernel: [158412.855226] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:19:45 localhost kernel: [158412.855240] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Sep 27 10:20:27 localhost kernel: [158455.095601] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:20:27 localhost kernel: [158455.096105] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:20:29 localhost kernel: [158457.655674] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 27 10:20:29 localhost kernel: [158457.656163] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 27 10:20:29 localhost kernel: [158457.656179] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Sep 27 10:21:30 localhost kernel: [158518.696847] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -1
10
Sep 27 10:21:33 localhost kernel: [158521.256909] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -1
10

I had to reboot the unit in order to recover connectivity.

iwconfig:

root@rpi4-1:/var/log# iwconfig
wlan0 IEEE 802.11 Mode:Master Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

eth0 no wireless extensions.

lo no wireless extensions.

My WiFi country is set to US.

I am running my RPi4 as a router between a network with about 10 of Raspberry Pi Zero's w/ WiFi.
I've seen a lot of weird behavior since I created this network.

My RPi Z's are on a 10.0.0.0/23 subnet, and the WiFI on the RPi 4 is routing packets to a 192.168.1.0/24 network.
I am trying to push data to a mysql database from the RPi Z's to a machine on the 192.168.1.0/24 network.
I don't know for sure if the WiFi on the RPi4 is causing the issues with the network connectivity between the two networks; it might just be that the RPi Z's are having trouble. But if I have any more data points to add to all of this, I'll add them.

I'm running an updated Raspbian Buster on all the RPi's.

[mukulb]

I am having issue with WiFi connectivity. It is automatically disconnecting some times.

[mikejc58]

I am having exactly the same problem on a Pi 4. This system had been working fine, but now has started getting:

Code: Select all

Sep 30 05:23:52 raspberrypi kernel: [33149.111253] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
Sep 30 05:23:54 raspberrypi kernel: [33151.596364] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Sep 30 05:23:54 raspberrypi kernel: [33151.596838] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Sep 30 05:23:54 raspberrypi kernel: [33151.596857] brcmfmac: brcmf_run_escan: error (-110)
Sep 30 05:23:54 raspberrypi kernel: [33151.596875] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Sep 30 05:24:54 raspberrypi kernel: [33211.597305] brcmfmac: brcmf_run_escan: error (-110)
Sep 30 05:24:54 raspberrypi kernel: [33211.597322] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Sep 30 05:25:54 raspberrypi kernel: [33271.598295] brcmfmac: brcmf_run_escan: error (-110)
   .
   .
   .

and the WiFi is dead until a reboot. After reboot, everything is fine, usually for hours, but eventually the WiFi dies in this way.

I did some googling for this problem and found this:

https://bugs.launchpad.net/ubuntu/+sour ... ug/1836730

which describes this problem as a mismatch in firmware levels in the packages "Linux-firmware" and "Linux-firmware-raspi2", both of which contain some of the same files.

I didn't understand the "solution" to copy these files from github.com/RPi-Distro. I have no idea to where I would copy these files.

[mikejc58]

I did some googling for this problem and found this:

https://bugs.launchpad.net/ubuntu/+sour ... ug/1836730

which describes this problem as a mismatch in firmware levels in the packages "Linux-firmware" and "Linux-firmware-raspi2", both of which contain some of the same files.

I didn't understand the "solution" to copy these files from github.com/RPi-Distro. I have no idea to where I would copy these files.

I found where these files reside (/lib/firmware/brcm/) and copied the files from github, but, in fact, they were identical to the files that I already had and I still have the problem. This is happening several times per day, at seemingly random times. The most recent occurred at 3:40 am, while I was asleep and the system was idle.

[AthlonFX]

You might give the updated Broadcom firmware a try.

[mikejc58]

You might give the updated Broadcom firmware a try.

Thanks. This updated firmware seems to have solved my other problem (loss of connection to wireless mouse), but, unfortunately, this problem continues to happen.

[mikejc58]

I give up!

The latest firmware and Raspbian updates have solved nothing. On my Pi4, the internal Wifi is simply unusable since the firmware "halts" killing the Wifi until the next reboot. This is happening randomly (sometimes only 10 minutes after reboot, sometimes 10 hours).

Perhaps someone else can get the experts interested. I have switched to a USB Wifi adapter which has been flawless for the last 4 days.

Mike

[kwasmich]

I had no WiFi issues on my RPi 3B+ with Stretch since I bought it, but I am facing the same issue constantly since I upgraded to Buster.

I thought that I might have installed or configured something wrong. But even on a freshly burned Image the issue pops up after just 12 hours.

I try the suggested firmware update from GitHub.
If this does not work I'll try older releases of Raspbian.

I'll not give in!

[kwasmich]

So far every Buster release is affected.
I'm going back in time even further.


UPDATE:
I went all the way back to Stretch 2018-03-13 and it also exposes this issue.
As I used exactly this Raspberry Pi 3 Model B+ with a Stretch release for almost a year without issues, it must be the firmware upgrade I did with rpi-update.

UPDATE 2:
So far my progress is somewhat disappointing.
* Take the latest Raspbian 2019-09-26-full.
* Downgrade the firmware and kernel using

Code: Select all

sudo rpi-update f8060224e53e26cdaea5b9f6f010ac8c3692e2ea

Fixes the WiFi issue but breaks HDMI, and USB (rendering the device usable only for headless usecases)
Running

Code: Select all

sudo apt update && sudo apt dist-upgrade

fixes HDMI and USB but breaks WiFi again

[kwasmich]

I'm running out of ideas.

I tried all official Raspbian releases since release of the Pi 3 B+ plain vanilla and with sudo apt dist-upgrade.
I tried the latest firmware via:

Code: Select all

wget http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_20190114-1+rpt4_all.deb
sudo dpkg -i firmware-brcm80211_20190114-1+rpt4_all.deb 

I tried reducing the speed and channel width on my router from 802.11ac with 80MHz to 802.11n with 40MHz channel width.

The only thing I haven't tried yet is to use 2.4GHz WiFi.
But that would defeat the reason why I bought the Raspberry Pi 3 Model B+ in the first place.

[mathieson]

Think I'm seeing something similar -

Had a 3B running fine for quite a while, not doing much. So decided to repurpose it as a NFS server for some cluster fun.

Added a shield and drive - reboot, and now the wireless (which it's been connected to for months) no longer connects. Click it on the GUI, and it'll connect without error, but doesn't do anything or actually connect.

So, ok, I hosed something. Check no other computers have a problem. Nope. Add a new Pi 4, and it connects no problem.

OK, so maybe it's a bug with the older version of Raspbian? Download the new one, wipe the Pi 3, and reinstall. Works fine, see that it connects to wifi. Yay!

Except - once I put the case on, the wifi disconnects, and same thing of failing to reconnect. OK, take the case off - maybe it's some bizarre Gaussian cage thing? It works! Except .. . . pretty soon it then disconnects again, and doesn't reconnect.

I have tried setting the power saving to not work, to avoid it dropping. Not sure I did that correctly, but the behavior does persist, and can't believe that the default behavior is to drop after 3 min and never come back even when attempted. Anyone else seeing something like this?

[kwasmich]

I am running out of ideas.
I had it running for 3.5 days without trouble and I thought I've narrowed down the issue.
I was away from home for a that time and so not much was going on in the Wi-Fi. So I created a dedicated 5 GHz Wi-Fi solely used by the Pi 3 B+.
In my head I mad up possible causes like some bad packages being transmitted from other devices, or a received packet counter that overflows.
But after just a few hours it again completely stopped working.

In my desperation I also tried 2.4 GHz Wi-Fi (which completely defeats why I bought it in the first place).
But there again the firmware was halted after a few hours.

I ran out of ideas. This is very frustrating. I spent over a month trying to nail down the issue and I've got nothing so far.

If some engineer has some beta firmware to try, I'd be glad to try it and report any debug information that would help solving the Issue.

[melopsitaco]

I am having the same problems on a rpi 4 with GB.

Code: Select all

# apt-cache policy firmware-brcm80211
firmware-brcm80211:
  Installed: 1:20190114-1+rpt4
  Candidate: 1:20190114-1+rpt4
  Version table:
 *** 1:20190114-1+rpt4 500
        500 http://archive.raspberrypi.org/debian buster/main armhf Packages
        100 /var/lib/dpkg/status
     20190114-2 500
        500 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Packages

And I get the following error at random times:

Code: Select all

[10641.936750] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[10641.937235] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[10641.937252] brcmfmac: brcmf_run_escan: error (-110)

[199109.715466] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[199169.716774] brcmfmac: brcmf_run_escan: error (-110)
[199169.716790] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[199229.798149] brcmfmac: brcmf_run_escan: error (-110)

[ronkinoz]

Same problem here with Pi4/4GB running fully up to date Buster. WiFi eventually drops off and is not recoverable until reboot.

Makes the Pi useless as a media server. Not happy.

[lukemackinnon]

Unfortunately I have the same issues with my Pi 4. Its headless, running only homebridge, but after a random amount of time the wifi craps out and can't be restart without a reboot.

Have read on other forums that UHD resolutions on the HDMI interface can cause the issue, I have dropped the res back to 1080. No luck... same wifi issues.

Lastest firemare and software.... here are all my dets for what its worth:-
pi@raspberrypi:~ $ cat /etc/rpi-issue
Raspberry Pi reference 2020-02-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 5f884374b6ac6e155330c58caa1fb7249b8badf1, stage5

pi@raspberrypi:~ $ vcgencmd version
Feb 12 2020 12:36:21
Copyright (c) 2012 Broadcom
version c3c8dbdf147686fb0c3f32aece709d0653368810 (clean) (release) (start)

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux

pi@raspberrypi:~ $ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11 ESSID:"macknet"
Mode:Managed Frequency:5.18 GHz Access Point: 9C:3D:CF:FA:B9:6D
Bit Rate=292.5 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=43/70 Signal level=-67 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.


/var/log/syslog
Mar 2 07:49:56 raspberrypi kernel: [47477.725480] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Mar 2 07:50:56 raspberrypi kernel: [47537.725606] brcmfmac: brcmf_run_escan: error (-110)
Mar 2 07:50:56 raspberrypi kernel: [47537.725621] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Mar 2 07:51:56 raspberrypi kernel: [47597.725766] brcmfmac: brcmf_run_escan: error (-110)
Mar 2 07:51:56 raspberrypi kernel: [47597.725781] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Mar 2 07:52:56 raspberrypi kernel: [47657.725879] brcmfmac: brcmf_run_escan: error (-110)
Mar 2 07:52:56 raspberrypi kernel: [47657.725894] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Mar 2 07:53:56 raspberrypi kernel: [47717.726011] brcmfmac: brcmf_run_escan: error (-110)


pi@raspberrypi:~ $ dmesg | grep brcmfmac
[ 5.028743] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 5.038222] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 5.041749] usbcore: registered new interface driver brcmfmac
[ 5.277687] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 5.291870] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 8.126774] brcmfmac: power management disabled


It would be awesome if an eng or eggspert could help us out.... this is very frustrating. Have resort to a cron job that runs a shutdown/reboot if the pings fail... feels very caveman like.

Given its happening on Pi 3 and 4 devices it seems unlikely to be hardware... so there feels to me like there is a solution out there. Hope it comes our way soon... Happy to help and anyone who wants to help us solve this.

[sve]

Hi,

I'm also having this issue with a fully updated RPI 3+

It worked fin until a few weeks ago, after the pi-firmware was updated.

In my case the RPi is my main WiFi AP (via hostpad) and it's a headless server, so I let you imagine how frustrating that is especially now that I'm covid19-confined home and have to home work. Fortunately it also has pivpn installed so using 4G on my phone I can connect to it and do a proper reboot instead of unplugigng the adapter.

It can work fine for 20 hours, then fail 3 times within the next 30 minutes, then fine again for a few hours, etc.

Here's the output of sudo dmesg | grep brcmfmac:

Code: Select all

[    5.977832] brcmfmac: F1 signature read @0x18000000=0x15264345
[    5.985332] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.986070] usbcore: registered new interface driver brcmfmac
[    6.263047] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    6.280890] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar  2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2
[   15.165377] brcmfmac: power management disabled

uname -a:

Code: Select all

Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l GNU/Linux

Is there any confirmation that someone who knows how to fix this is looking at it?

More importantly, is there anything I can do to help? Tests to make, log output to provide?

Thanks

[dave_the_troll]

No help here, but some data:
Pi Zero W
Buster - updated,
the WIFI loss seems to be traffic related. I.E. I can run for several hours keeping the little thing busy. But when I start file transfers ( I'm taking 200KB pictures 1 per second, 2MB every 2 min. ) it rarely beats 1/2 hr. ( Had tried scp for every pic. )
Then tried rsync. Same story. Shifted to pull ( rsync from a Pi3B ( Cat5to router, WIFI to Pi Zero W ). Got one 20MB transfer ( amybe bigger ). Found that while the XRDP session was dead, and the Zero and the 3B were not talking, the Zero was still live - for a bit.
Tried shifting to SFTP using FileZilla. About the same result. I uninstalled XRDP and left X off, running from terminal. FileZilla again pulled ~100 2MB files. Disconnect "brcmf_run_cscan: scan error (--100)" . - Which it keeps repeating,

"[ 3101.xxxx]brcmfmac: brcmf_run_cscan: scan error (--100)
"[ 3101.xxxx] brcmfamc: brcmf_cfg80211_scan: scan error (--110)
next pair at { 3161.xxx...] then 3221.xxx .....

so, something is _trying_ to heal, but failing. And when I poke around, I usually end up with it hung.
---- ( don't know enough to ask it questions--- free looks good, it _says_ wlan _correction_ it _said_ wlan0 was up and connected, now it says no wireless - ifconfig only shows loopback.

sudo ip link set wlan0 down
sudo ip link set wlan0 up

now ifconfig shows wlan0, says it's up no IP address.

Anybody know anything else I should ask it?

dave

[RobertB]

I have a Raspberry Pi 4 which has issues with the wireless as well.
Starts throwing errors at least once every 24 hour:
Apr 5 00:19] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
[ +2.466183] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ +0.000460] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ +0.000016] brcmfmac: brcmf_run_escan: error (-110)



Apr 6 03:34] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
[ +2.482174] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ +0.000450] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ +0.000017] brcmfmac: brcmf_run_escan: error (-110)
[ +0.000014] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[Apr 6 03:35] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ +0.000440] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ +0.000015] brcmfmac: brcmf_run_escan: error (-110)

Updated to Stable firmware. No difference. Not running at 2560x1440. Tries running at 5Ghz instead of 2.4Ghz. No difference -- still shuts down the wireless and requires a reboot.

Not brave enough to go to Beta firmware as I did not see anything in the readmes which led me to believe it might be fixed.
Anyone gets a good fix for this (besides a wireless dongle), let us know.

[sve]

Hi all,

There is a solution!

It is possible to use a previous version of the Broadcom firmware from Cypress. I did that a couple of days ago and have been using the network quite intensively. It is my main WiFi AP, so all the devices in the house directly connect to it, and I've been copying gigabytes of data between the RPi and a PC without any issue.

I found this GitHub post and followed a few other links here and there to revert the Broadcom firmware.

Here are detailed commands:

Code: Select all

cd ~
wget  https://community.cypress.com/servlet/JiveServlet/download/19000-1-51721/cypress-fmac-v4.14.77-2020_0115.zip
unzip cypress-fmac-v4.14.77-2020_0115.zip -d cypress
cd cypress
gunzip cypress-firmware-v4.14.77-2020_0115.tar.gz
tar xvf cypress-firmware-v4.14.77-2020_0115.tar
cd /lib/firmware/
cp -R brcm /home/pi/brcm.old
cd brcm
rm -rf *
cp -R /home/pi/cypress/firmware/* .
reboot now

Explanations: these commands download a zip containing the required files (line 2); decompress that in a folder named 'cypress' in your home directory (lines 3 to 6); backup the current firmware files just in case (lines 7 and 8); remove the current firmware and replace it with the files you downloaded/decompressed earlier (lines 9 and 10) and then reboot to make sure the firmware is properly loaded (line 11)

Some commands require root access (the last 2 for sure), so use sudo in front of them. Sometimes sudo won't work (sudo cd somedir doesn't seem to work very nice); if so do those commands as the root user.

Obligatory disclaimer: I'm not responsible if it breaks something, do at your own risk!

Cheers.

[RemyG]

Hi all,

There is a solution!

It is possible to use a previous version of the Broadcom firmware from Cypress. I did that a couple of days ago and have been using the network quite intensively. It is my main WiFi AP, so all the devices in the house directly connect to it, and I've been copying gigabytes of data between the RPi and a PC without any issue.

I found this GitHub post and followed a few other links here and there to revert the Broadcom firmware.

Here are detailed commands:

Code: Select all

cd ~
wget  https://community.cypress.com/servlet/JiveServlet/download/19000-1-51721/cypress-fmac-v4.14.77-2020_0115.zip
unzip cypress-fmac-v4.14.77-2020_0115.zip -d cypress
cd cypress
gunzip cypress-firmware-v4.14.77-2020_0115.tar.gz
tar xvf cypress-firmware-v4.14.77-2020_0115.tar
cd /lib/firmware/
cp -R brcm /home/pi/brcm.old
cd brcm
rm -rf *
cp -R /home/pi/cypress/firmware/* .
reboot now

Explanations: these commands download a zip containing the required files (line 2); decompress that in a folder named 'cypress' in your home directory (lines 3 to 6); backup the current firmware files just in case (lines 7 and 8); remove the current firmware and replace it with the files you downloaded/decompressed earlier (lines 9 and 10) and then reboot to make sure the firmware is properly loaded (line 11)

Some commands require root access (the last 2 for sure), so use sudo in front of them. Sometimes sudo won't work (sudo cd somedir doesn't seem to work very nice); if so do those commands as the root user.

Obligatory disclaimer: I'm not responsible if it breaks something, do at your own risk!

Cheers.

Hi sve,

I've the same issue on my Pi 3b+. The instability appears when there is a lot of traffic on the wifi interface.

Could you please post the link of the github discussion? I don't know the "cypress" community and don't understant why it is not proposed to revert to an older firmware available on raspberrypi archive.

Thanks.

[RemyG]

Hi all,

I installed the cypress firmware with no joy : my wlan interface has wanished.

*****Therefore, I found a stable solution by restoring an old firmware from the raspberrypi archive:*****

Code: Select all

wget https://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_20161130-3+rpt3_all.deb
sudo dpkg -i firmware-brcm80211_20161130-3+rpt3_all.deb
sudo reboot

This one worked perfectly for my 3B+ and my wifi link is now back to nominal

Hope a future update will solve definitively the issue.

++