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

wlan freezes in raspberry pi 3B+ #2453

Open
ghost opened this issue Mar 19, 2018 · 205 comments
Open

wlan freezes in raspberry pi 3B+ #2453

ghost opened this issue Mar 19, 2018 · 205 comments

Comments

@ghost
Copy link

@ghost ghost commented Mar 19, 2018

(see also #1342 )

I've also got that problem with wifi dying.

Mar 17 18:25:28 hassass kernel: [10279.186321] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
Mar 17 18:25:30 hassass kernel: [10281.665090] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Mar 17 18:25:30 hassass kernel: [10281.665622] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Mar 17 18:25:30 hassass kernel: [10281.665638] brcmfmac: brcmf_run_escan: error (-110)
Mar 17 18:25:30 hassass kernel: [10281.665647] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Mar 17 18:26:30 hassass kernel: [10341.665866] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout

This is with 4.14.27-v7+ and with
/sbin/iw dev wlan0 set power_save off
/sbin/ifconfig wlan0 promisc
in /etc/rc.local.

[    4.112717] brcmfmac: F1 signature read @0x18000000=0x15264345
[    4.119827] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[    4.120314] usbcore: registered new interface driver brcmfmac
[    4.440371] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb
27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    4.440958] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2
Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09
18:56:28
[   10.911757] brcmfmac: power management disabled
[   12.016088] brcmfmac: power management disabled
[ 2074.090674] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg
failed w/status -5
[ 2074.090687] brcmfmac: brcmf_cfg80211_get_tx_power: error (-5)
[ 2074.090745] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2074.090753] brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-5)
[ 2074.610583] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2074.611992] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2074.613945] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2074.613971] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[ 2074.729716] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2074.729733] brcmfmac: brcmf_cfg80211_reg_notifier: Country code iovar
returned err = -5
[ 2074.871693] usbcore: deregistering interface driver brcmfmac
[ 2074.929084] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 2074.936897] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 2074.937139] usbcore: registered new interface driver brcmfmac
[ 2075.118180] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb
27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 2075.118706] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2
Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09
18:56:28
[ 2075.215365] brcmfmac: power management disabled
[ 2075.263751] brcmfmac: power management disabled
[ 2085.475001] brcmfmac: power management disabled
[ 2124.380808] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2124.381146] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2124.381156] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[ 2124.622345] usbcore: deregistering interface driver brcmfmac
[ 2124.705432] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 2124.714194] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 2124.716213] usbcore: registered new interface driver brcmfmac
[ 2124.929556] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb
27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 2124.929993] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2
Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09
18:56:28
[ 2125.105218] brcmfmac: power management disabled
[ 2125.150290] brcmfmac: power management disabled
[ 8237.434034] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content:
0x40012
[ 8239.890302] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 8239.890822] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 8239.890835] brcmfmac: brcmf_run_escan: error (-110)
[ 8239.890845] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[ 8254.280425] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg
failed w/status -5
[ 8254.280438] brcmfmac: brcmf_cfg80211_get_tx_power: error (-5)
[ 8254.280491] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8254.280498] brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-5)
[ 8254.800394] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8254.803873] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8254.808353] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8254.808370] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[ 8254.881402] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8254.881420] brcmfmac: brcmf_cfg80211_reg_notifier: Country code iovar
returned err = -5
[ 8255.001550] usbcore: deregistering interface driver brcmfmac
[ 8255.071184] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 8255.077098] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 8255.077348] usbcore: registered new interface driver brcmfmac
[ 8257.730418] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 8257.751038] brcmfmac: brcmf_c_get_clm_name: retrieving revision info
failed (-110)
[ 8257.751049] brcmfmac: brcmf_c_process_clm_blob: get CLM blob file name
failed (-110)
[ 8257.751068] brcmfmac: brcmf_c_preinit_dcmds: download CLM blob file
failed, -110
[ 8257.751076] brcmfmac: brcmf_bus_started: failed: -110
[ 8257.751114] brcmfmac: brcmf_sdio_firmware_callback: dongle is not
responding
[ 8304.417684] usbcore: deregistering interface driver brcmfmac
[ 8304.486099] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 8304.493613] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 8304.494078] usbcore: registered new interface driver brcmfmac
[ 8304.686761] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb
27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 8304.687203] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2
Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09
18:56:28
[ 8304.829994] brcmfmac: power management disabled
[ 8304.907662] brcmfmac: power management disabled
[ 8357.441791] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content:
0x40012
[ 8359.891146] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 8359.891655] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 8359.891668] brcmfmac: brcmf_run_escan: error (-110)
[ 8359.891677] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[ 8371.731226] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 8371.731731] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 8371.731746] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
[ 8373.941267] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg
failed w/status -5
[ 8373.941280] brcmfmac: brcmf_cfg80211_get_tx_power: error (-5)
[ 8373.941330] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8373.941338] brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-5)
[ 8374.461245] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8374.461942] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8374.463553] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8374.463573] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[ 8374.564729] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 8374.564750] brcmfmac: brcmf_cfg80211_reg_notifier: Country code iovar
returned err = -5
[ 8374.702401] usbcore: deregistering interface driver brcmfmac
[ 8374.759839] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 8374.767561] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 8374.771137] usbcore: registered new interface driver brcmfmac
[ 8377.411255] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 8377.431924] brcmfmac: brcmf_c_get_clm_name: retrieving revision info
failed (-110)
[ 8377.431934] brcmfmac: brcmf_c_process_clm_blob: get CLM blob file name
failed (-110)
[ 8377.431941] brcmfmac: brcmf_c_preinit_dcmds: download CLM blob file
failed, -110
[ 8377.431949] brcmfmac: brcmf_bus_started: failed: -110
[ 8377.432003] brcmfmac: brcmf_sdio_firmware_callback: dongle is not
responding
[ 8424.133114] usbcore: deregistering interface driver brcmfmac
[ 8424.229631] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 8424.237210] brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 8424.239352] usbcore: registered new interface driver brcmfmac
[ 8424.460736] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb
27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 8424.461174] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2
Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09
18:56:28
[ 8424.646993] brcmfmac: power management disabled
[ 8424.708633] brcmfmac: power management disabled
@ghost ghost changed the title wlan freezes in raspberry pi 3+ wlan freezes in raspberry pi 3B+ Mar 19, 2018
@digisaster
Copy link

@digisaster digisaster commented Mar 21, 2018

Same problem here.

If i do a:
sudo BRANCH=next rpi-update
Then i have a working situation.
After this i got:
uname -a
Linux raspberrypi 4.14.17-v7+ #1090 SMP Mon Feb 5 21:02:18 GMT 2018 armv7l GNU/Linux

So i guess its kernel related.

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Mar 21, 2018

Interesting. So not in the current rpi-update, but in the next branch? Should make the particular change a bit easier to find.

@ghost
Copy link
Author

@ghost ghost commented Apr 21, 2018

any news?

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Apr 23, 2018

Not had a chance to look yet. How do you provoke the problem? We've not had many reports on B+ Wifi failing in this way, so apparently it's unusual. Have you updated to the very latest 4.14.xx kernel? Does that make any difference?

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Apr 23, 2018

Once I have more details on how to replicate the issues, I can send the data to Cypress for investigation. The mailbox error, IIRC, is a firmware crash, so its not something we can really deal with here, since we do not have access to the firmware.

@llamasoft
Copy link

@llamasoft llamasoft commented May 25, 2018

It may be slightly off topic because it's a different distribution, but it's pretty easy to trigger this error when using Kali Pi.
Putting the device into monitor mode (using mon0up in Kali-Pi) and running aireplay-ng --test causes it to emit the Unknown mailbox data content: 0x40012 error almost immediately. From then on, the wifi is worthless until you reboot.

For reference, mon0up is a short shell script that runs iw phy phy0 interface add mon0 type monitor and ifconfig mon0 up and displays some brief info.

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 5, 2018

On a project I am working on, I am getting this constantly with Kali Pi when in monitor mode. Unloading and reloading the driver works sometimes and sometimes not. Sometimes it happens after 5 seconds, sometimes after 5 minutes, very random. Verified its not a hardware problem since I have 2 Pi's and both do it. I also loaded Raspbian latest and installed latest Nextmon drivers and I get the exact same thing, Kernel is 4.14.30-Re4son-v7+ on Kali. Don't have other offhand.

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Jun 6, 2018

Do you get any errors listed in dmesg?

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 6, 2018

@Nemesis7
Copy link

@Nemesis7 Nemesis7 commented Jun 9, 2018

Any news about this? I'm having this same issue. From dmesg:

[ 4.584121] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 4.868470] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 4.869048] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28

I wish I never executed the rpi-update; I finally got the Raspberry Pi 3 B+ working as an AP + Managed Wifi at 5GHz, but now the AP doesn't work anymore after the update. How can I downgrade the brcmfmac to a stable/working version?

@gdb-power
Copy link

@gdb-power gdb-power commented Jun 10, 2018

After "Unknown mailbox data content: 0x40012" is received,
sometimes the communication can be recovered with the following commands:

modprobe -r brcmfmac
modprobe brcmfmac

Sometimes it doesn't recover even after modprobe -r (device is stuck).
In that case, the following heavy-handed commands will fix the communication with the wifi device:

echo -n "3f300000.mmc" > /sys/devices/platform/soc/3f300000.mmc/driver/unbind
sleep 1
echo -n "3f300000.mmc" > /sys/bus/platform/drivers/mmc-bcm2835/bind

technical comment:
rebinding the mmc driver will call probe(),
which will call mmc:bcm2835_reset_internal(),
which will power-cycle the SDIO device (SDVDD_POWER_OFF),
which will properly reset & re-detect the wedged WIFI SDIO device. Phew!

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 10, 2018

@pelwell
Copy link
Contributor

@pelwell pelwell commented Jun 10, 2018

@Nemesis7 You can revert to any previous firmware+kernel package using rpi-update by putting the hash (string of hexadecimal digits) on the command line. The hashes can be found on the right hand side of the list of commits (releases): https://github.com/Hexxeh/rpi-firmware/commits/master

Alternatively you could return to the standard Raspbian kernel using:

sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 11, 2018

The heavy handed method seems to be working to get the driver working again, but is there a chance of this being fixed so its not necessary? Is this a hardware or firmware issue? Thank you

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Jun 12, 2018

@cdouglas97 We currently do not know the cause of this. The mailbox error is the result of the firmware on the wireless chip dying, but the cause of that is unclear. We do NOT have access to the firmware source, that is provided as a binary by Cypress so we do rely on them to fix firmware issues.

I'm not looking at it at the moment, I have some other stuff to clear first. However, if anyone has a clear set of steps to replicate the problem on Raspbian, that would be very useful once I do start to look at it.

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 12, 2018

Thank you. I can reproduce it very easily. Steps:

wlan0 is not up, only active interface is eth0

Use Airmon-ng to create monitor port:

/usr/sbin/airmon-ng start wlan0

Run airodump that scans all 2.4 to 5.8Ghz frequencies

/usr/sbin/airodump-ng -C 2412-5825 --write-interval 10 --write OUTPUTME --output-format netxml wlan0mon

It usually happens within 30 seconds to 5 minutes. I run the airodump for 60 seconds at a time with a 15 min gap between runs and then kill it so sometimes it completes its run and sometimes not. I added the heavy-handed commands before I start and it didn't seem to make a difference on how long it took for it to die. It just fixed the firmware if it died during a previous run.

-Chris

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Jun 12, 2018

@cdouglas97 I am not familiar with airmon/airodump. What package do I need to install in Raspbian to get those?

@pelwell
Copy link
Contributor

@pelwell pelwell commented Jun 12, 2018

sudo apt-get install aircrack-ng

@pelwell
Copy link
Contributor

@pelwell pelwell commented Jun 12, 2018

With wlan0 available but not associated with an AP I get:

pi@raspberrypi:~ $ sudo airmon-ng start wlan0

Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to run 'airmon-ng check kill'

  PID Name
  319 avahi-daemon
  353 dhcpcd
  364 avahi-daemon
  400 wpa_supplicant

PHY	Interface	Driver		Chipset

phy0	wlan0		brcmfmac	Broadcom 43430


ERROR adding monitor mode interface: command failed: Operation not supported (-95)

Any suggestions?

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 12, 2018

pelwell, the default Rasbian latest install firmware doesn't allow monitoring, have to use this: https://github.com/seemoo-lab/nexmon to make it work. Kali uses this and I took a Raspbian image a built patch as directed and both get same result.

@JamesH65
Copy link
Contributor

@JamesH65 JamesH65 commented Jun 12, 2018

Er, so the way to make this go wrong is to install some random third party stuff that plays around with the firmware in a way that probably wasn't intended by the developers? Why am I not surprised this might go wrong?

Unless this goes wrong with our standard firmware, I'm not sure we should spend any more time on this.

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 12, 2018

I don't blame you, I thought that it was understood from the first post that said he was putting into promiscuous mode that's what we were doing. Unless was are supposed to be able to put default firmware into monitor mode making the nexmon unnecessary.

Thanks for your time and the command to force the wifi reload.

-Chris

@pelwell
Copy link
Contributor

@pelwell pelwell commented Jun 12, 2018

I don't know why you would think it should have been understood - promiscuous mode is not the same as monitor mode.

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 12, 2018

@cdouglas97
Copy link

@cdouglas97 cdouglas97 commented Jun 12, 2018

The OP might not be doing the same thing as I am with the nexmon fw since he is just trying promiscuous mode so it still might be something you can investigate for him.

@gdb-power
Copy link

@gdb-power gdb-power commented Jun 13, 2018

@pelwell @JamesH65 please don't give up on all of us who use the regular firmware... It is a real problem.

In the following conditions, the firmware crashes several times per day:

  1. Raspberry PI running in an environment with alot a diverse wifi packets, such as a busy train station or a busy mall. Not a "regular" office environment or a shielded RF room...

  2. Raspberry PI running as hotspot (thus continuously listening to incoming packets), preferably on a busy 2.4GHz channel (1,6,11), not on a clean 5GHz channel. There is no need for stations to be connected to the hotspot.

Note: the raspberry PI wifi crashes randomly in any environment and also when running just as station (not AP). I'm just describing the conditions that increase the probability of crashing.

@pelwell
Copy link
Contributor

@pelwell pelwell commented Jun 13, 2018

Nobody's giving up. We have a number of difficult problems ongoing, and the Ethernet stalls are currently getting most of the attention, but now we have what should be a low-impact workaround for that the spotlight will turn to this issue (which looks suspiciously like an old Pi3B problem).

@ganeshs4
Copy link

@ganeshs4 ganeshs4 commented Jun 30, 2020

Thanks @pelwell. Yes I do see below on rpi3B+:

dmesg | grep brcmfmac43 [ 5.044706] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 5.333213] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

Is there a test firmware for brcmfmac43455? The one which was provided above was brcmfmac43430 and somehow it did fix my raspberry pi3B+ and the wifi hasn't stopped working for 2days now (but as you said it must be fluke and it didn't actually fix the issue).

@ganeshs4
Copy link

@ganeshs4 ganeshs4 commented Jul 1, 2020

For raspberry pi3b+ the patch version which I used is here - raspberrypi/firmware#1403 (comment) (it needs to be 43455 - for rpi3b+).

Note from @pelwell -
43430 is used on 3B and Zero W, while 43455 is on 3B+, 3A+ and 4B.
Source: raspberrypi/firmware#1403 (comment)

@pelwell
Copy link
Contributor

@pelwell pelwell commented Jul 1, 2020

That version of the firmware is now in the RPi-Distro/firmware-nonfree repo and will be in future package and image releases. It's version string is:

43455c0-roml/43455_sdio-pno-aoe-pktfilter-pktctx-lpc-pwropt-43455_ftrs-wfds-mfp-dfsradar-wowlpf-idsup-idauth-noclminc-clm_min-obss-obssdump-swdiv Version: 7.45.206 (r725000 CY) CRC: 3d58e5fe Date: Mon 2020-03-23 02:21:50 PDT Ucode Ver: 1043.2139 FWID 01-88ee44ea

@frankweyns
Copy link

@frankweyns frankweyns commented Jul 1, 2020

It is nice to see those new versions... But are they stable ? Did anyone tested it for more then 2 hours ? (with a bridge like RaspAP)
I am still on firmware-brcm80211_20161130-3+rpt3_all.deb which is the only stable one I found.

@hsjzmk
Copy link

@hsjzmk hsjzmk commented Jul 1, 2020

Hi.
My RPi 3B+ have the same problem too.
I tried the patch with the following steps. (Not brcmfmac43430, but 43455)

I patched the files which were available at https://community.cypress.com/docs/DOC-20044 on my raspberry pi 3B+ (even though the test firmware provided by @pelwell had worked). Steps for patching:

  1. downloaded the file from https://community.cypress.com/docs/DOC-20044
  2. unzipped cypress-firmware-v5.4.18-2020_0625.tar.gz and renamed the below 2 files:
    Before: cyfmac43430-sdio.bin & cyfmac43430-sdio.clm_blob
    Renamed to: brcmfmac43430-sdio.bin & brcmfmac43430-sdio.clm_blob
  3. now on raspberry pi - navigate to /lib/firmware/brcm and back up brcmfmac43430-sdio.bin & brcmfmac43430-sdio.clm_blob
  4. now copy the above files from step2 into /lib/firmware/brcm
  5. reboot

But unfortunately the problem did not improve.

I rebooted RPi at Jul 1 01:33:49.
And after rebooting, the first error message is:

Jul  1 16:38:40 raspberrypi kernel: [52519.017879] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
Jul  1 16:38:42 raspberrypi kernel: [52521.432582] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul  1 16:38:42 raspberrypi kernel: [52521.435979] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul  1 16:38:42 raspberrypi kernel: [52521.436002] brcmfmac: brcmf_run_escan: error (-110)
Jul  1 16:38:42 raspberrypi kernel: [52521.436013] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul  1 16:38:45 raspberrypi kernel: [52523.992588] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul  1 16:38:45 raspberrypi kernel: [52523.995971] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle

@ganeshs4
Copy link

@ganeshs4 ganeshs4 commented Jul 1, 2020

@hsjzmk - the one which you downloaded doesn't seem to have the potential fix. The firmware which @pelwell had provided was a test firmware. Please download the test firmware which is available in this comment - raspberrypi/firmware#1403 (comment)

@TrestleMonkey
Copy link

@TrestleMonkey TrestleMonkey commented Jul 2, 2020

@frankweyns The test f/w provided by @pelwell back here #2453 (comment) has been running in AP mode (with bridging) continually for 20+ days just fine. I haven't tried the more recent one though.

@hsjzmk
Copy link

@hsjzmk hsjzmk commented Jul 2, 2020

@ganeshs4 Thank you! I'll try this.

@jspanitz
Copy link

@jspanitz jspanitz commented Jul 25, 2020

My PI 3B+ is also having this issue. I grabbed the firmware mentioned here raspberrypi/firmware#1403 (comment) and here https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm. replaced the current file and rebooted. With 12 hours the problem occurred again.

$ cat /proc/device-tree/model
Raspberry Pi 3 Model B Plus Rev 1.3

$ dmesg | grep "brcmfmac.*Firmware"
[ 7.534561] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea

Syslog when lockup occurred:
https://pastebin.com/uJWjpiaE

Syslog when I restarted PI
https://pastebin.com/Lde8yesf

@monojk
Copy link

@monojk monojk commented Jul 30, 2020

I have the same problem on a 3B

$ cat /proc/device-tree/model
Raspberry Pi 3 Model B Rev 1.2

$ dmesg | grep "brcmfmac.*Firmware"
[ 3.988455] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378

@theute
Copy link

@theute theute commented Jul 31, 2020

Same:

[ 2240.325147] ieee80211 phy0: brcmf_run_escan: error (-110)
[ 2240.325163] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[ 2300.325075] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 2300.325547] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 2300.325793] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
                 lr   0x0007a093 pc   0x0007a094 offset 0x25f830
                 r0   0x00000036 r1   0x00000005 r2 0x00000000 r3 0x00000001
                 r4   0x002494d8 r5   0x00000000 r6 0x00249468 r7 0x00000004
[ 2300.325813] ieee80211 phy0: brcmf_run_escan: error (-110)
[ 2300.325828] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[ 2360.325710] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 2360.326196] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 2360.326445] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
                 lr   0x0007a093 pc   0x0007a094 offset 0x25f830
                 r0   0x00000036 r1   0x00000005 r2 0x00000000 r3 0x00000001
                 r4   0x002494d8 r5   0x00000000 r6 0x00249468 r7 0x00000004
[ 2360.326466] ieee80211 phy0: brcmf_run_escan: error (-110)
[ 2360.326481] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[ 2420.326282] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 2420.326756] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 2420.327004] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
                 lr   0x0007a093 pc   0x0007a094 offset 0x25f830
                 r0   0x00000036 r1   0x00000005 r2 0x00000000 r3 0x00000001
                 r4   0x002494d8 r5   0x00000000 r6 0x00249468 r7 0x00000004
[ 2420.327027] ieee80211 phy0: brcmf_run_escan: error (-110)
[ 2420.327044] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[ 2480.326830] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 2480.327297] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 2480.327545] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
                 lr   0x0007a093 pc   0x0007a094 offset 0x25f830
                 r0   0x00000036 r1   0x00000005 r2 0x00000000 r3 0x00000001
                 r4   0x002494d8 r5   0x00000000 r6 0x00249468 r7 0x00000004
[ 2480.327565] ieee80211 phy0: brcmf_run_escan: error (-110)
[ 2480.327580] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[ 2540.327356] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 2540.327818] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 2540.328065] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
                 lr   0x0007a093 pc   0x0007a094 offset 0x25f830
                 r0   0x00000036 r1   0x00000005 r2 0x00000000 r3 0x00000001
                 r4   0x002494d8 r5   0x00000000 r6 0x00249468 r7 0x00000004
[ 2540.328085] ieee80211 phy0: brcmf_run_escan: error (-110)
[ 2540.328099] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[ 2600.327837] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 2600.328330] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 2600.328576] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
                 lr   0x0007a093 pc   0x0007a094 offset 0x25f830
                 r0   0x00000036 r1   0x00000005 r2 0x00000000 r3 0x00000001
                 r4   0x002494d8 r5   0x00000000 r6 0x00249468 r7 0x00000004

@henrym9
Copy link

@henrym9 henrym9 commented Aug 17, 2020

I've got four pi's, three of which are having this issue. My home wireless is provided by an Orbi RBR20 mesh system running firmware 2.5.1.16 with about 25-30 clients on it. The only ones having issues are the pis.

All the Pis having issues have this in common:

dmesg | grep "brcmfmac.*Firmware"
[ 5.943583] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2

The pi not having issues is an older 3B running a different chip and firmware:

BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd

Syslogs are all similar to this:
Aug 17 03:52:35 RaspberryPints kernel: [31277.147188] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
Aug 17 03:52:37 RaspberryPints kernel: [31279.560593] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 17 03:52:37 RaspberryPints kernel: [31279.561143] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Aug 17 03:52:37 RaspberryPints kernel: [31279.561433] brcmfmac: dongle trap info: type 0x4 @ epc 0x0007a094
Aug 17 03:52:37 RaspberryPints kernel: [31279.561433] cpsr 0x6000019f spsr 0x600001bf sp 0x0025f888
Aug 17 03:52:37 RaspberryPints kernel: [31279.561433] lr 0x0007a093 pc 0x0007a094 offset 0x25f830
Aug 17 03:52:37 RaspberryPints kernel: [31279.561433] r0 0x00000036 r1 0x00000005 r2 0x00000000 r3 0x00000001
Aug 17 03:52:37 RaspberryPints kernel: [31279.561433] r4 0x002494d0 r5 0x00000000 r6 0x00249460 r7 0x00000004
Aug 17 03:52:37 RaspberryPints kernel: [31279.561457] ieee80211 phy0: brcmf_run_escan: error (-110)
Aug 17 03:52:37 RaspberryPints kernel: [31279.561476] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
Aug 17 03:53:37 RaspberryPints kernel: [31339.561917] ieee80211 phy0: brcmf_run_escan: error (-110)
Aug 17 03:53:37 RaspberryPints kernel: [31339.561940] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)

@meliodasren
Copy link

@meliodasren meliodasren commented Sep 25, 2020

Just posting this here for reference:
iiab/iiab#823 (comment)

It looks like a project that uses the Pi as an AP so that clients can connect and access educational material while offline.

Anyhow, if I understand that table correctly, then it's almost like the last official firmware from Broadcom was rock solid (back in 2015) while every release since then from Cypress has crashed on them. As a result, it looks like they've reverted back to that original firmware for their project to get the stability/throughput that they need.

It looks like version 7.45.18.0 from 2015 is the only one that didn't crash and can support 32 clients connected simultaneously to the Pi. Whereas every version from 7.45.132 in 2018 to 7.45.214 in 2020 all crash and support less clients.

My own personal takeaway from this (not sure how accurate it is though), is that if you want a Pi 3B+/4 with stable WiFi then you need that original 7.45.18.0 firmware. If you want packet injection/monitor mode with nexmon for stable pen testing then you're out of luck at the moment with the built-in WiFi. I'm not sure, but my guess is that 7.45.18.0 doesn't support injection or monitor mode.

From the table, the list of OSes that have 7.45.18.0:
Ubuntu 19.10.1, Raspbian 2017-11-29 & precursors e.g. Raspbian 2017-08-16

@smeierger
Copy link

@smeierger smeierger commented Oct 29, 2020

I have the same problem with my pi 3b+. With the firmware in raspian (Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY)), the wifi freeze when traffic occurs.
With the firmware from https://community.cypress.com/docs/DOC-20044 or the newest from https://community.cypress.com/docs/DOC-21490 the wifi works but my raspi stuck on 2.4Ghz.
at the moment i try the firmware from https://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_20161130-3+rpt3_all.deb and it seems to work

my wifi network used the same ssid for 2.4 and 5Ghz and i use a mesh. with the firmware from cypress the pi stuck on the mesh-master. with the firmware integrated in raspian or the older firmware from the .deb the pi switch directly to the better placed repeater

pi runs on buster lite 5.4.72-v7+ #1356 SMP Thu Oct 22 13:56:54 BST 2020 armv7l GNU/Linux

greetings from germany

@KnuckleBob
Copy link

@KnuckleBob KnuckleBob commented Jan 6, 2021

Will these patches make it into a firmware build for the RPi 3 B models?

@DaStivi
Copy link

@DaStivi DaStivi commented Mar 23, 2021

is this still an issue? as iam running octoprint having following firmware:

[   10.763771] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan  4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e

at 08:09 i powered on my printer and started the print.. and at 8:38 it lost the network connection!
its pretty much repating the error messsages until i rebooted the pi now...
and have random wifi freezes with following errors in kern.log:

Mar 23 08:09:08 octopi kernel: [81927.415465] usb 1-1.1.3: new full-speed USB device number 8 using dwc_otg
Mar 23 08:09:08 octopi kernel: [81927.549116] usb 1-1.1.3: New USB device found, idVendor=1d50, idProduct=6029, bcdDevice= 1.00
Mar 23 08:09:08 octopi kernel: [81927.549146] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 23 08:09:08 octopi kernel: [81927.549163] usb 1-1.1.3: Product: Marlin USB Device
Mar 23 08:09:08 octopi kernel: [81927.549178] usb 1-1.1.3: Manufacturer: marlinfw.org
Mar 23 08:09:08 octopi kernel: [81927.549194] usb 1-1.1.3: SerialNumber: 0C01201BAF4A09025D5E8F45F50020C7
Mar 23 08:09:08 octopi kernel: [81927.550836] cdc_acm 1-1.1.3:1.0: ttyACM0: USB ACM device
Mar 23 08:09:08 octopi kernel: [81927.552141] usb-storage 1-1.1.3:1.2: USB Mass Storage device detected
Mar 23 08:09:08 octopi kernel: [81927.553244] scsi host0: usb-storage 1-1.1.3:1.2
Mar 23 08:09:09 octopi kernel: [81928.617624] scsi 0:0:0:0: Direct-Access Marlin SDCard 01 1.0 PQ: 0 ANSI: 0 CCS
Mar 23 08:09:09 octopi kernel: [81928.619896] sd 0:0:0:0: Attached scsi generic sg0 type 0
Mar 23 08:09:09 octopi kernel: [81928.657142] sd 0:0:0:0: [sda] Attached SCSI removable disk
Mar 23 08:38:54 octopi kernel: [83713.096431] mmc1: Timeout waiting for hardware interrupt.
Mar 23 08:38:54 octopi kernel: [83713.096528] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Mar 23 08:38:54 octopi kernel: [83713.096562] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:38:54 octopi kernel: [83713.096774] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Mar 23 08:39:04 octopi kernel: [83723.336425] mmc1: Timeout waiting for hardware interrupt.
Mar 23 08:39:04 octopi kernel: [83723.336518] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Mar 23 08:39:04 octopi kernel: [83723.336536] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:04 octopi kernel: [83723.336736] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Mar 23 08:39:04 octopi kernel: [83723.336758] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Mar 23 08:39:14 octopi kernel: [83733.576413] mmc1: Timeout waiting for hardware interrupt.
Mar 23 08:39:14 octopi kernel: [83733.576507] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Mar 23 08:39:14 octopi kernel: [83733.576518] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:14 octopi kernel: [83733.576874] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:14 octopi kernel: [83733.576996] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:14 octopi kernel: [83733.577114] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:14 octopi kernel: [83733.577181] brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-84
Mar 23 08:39:14 octopi kernel: [83733.577224] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -84
Mar 23 08:39:24 octopi kernel: [83743.816433] mmc1: Timeout waiting for hardware interrupt.
Mar 23 08:39:24 octopi kernel: [83743.816516] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Mar 23 08:39:24 octopi kernel: [83743.816534] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:24 octopi kernel: [83743.816902] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
Mar 23 08:39:34 octopi kernel: [83754.056437] mmc1: Timeout waiting for hardware interrupt.
Mar 23 08:39:34 octopi kernel: [83754.056593] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:34 octopi kernel: [83754.056942] brcmfmac: mmc_submit_one: CMD53 sg block write failed -84
Mar 23 08:39:34 octopi kernel: [83754.056959] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:34 octopi kernel: [83754.057157] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -19
Mar 23 08:39:34 octopi kernel: [83754.057178] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -19
Mar 23 08:39:41 octopi kernel: [83760.994773] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:41 octopi kernel: [83760.996946] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:45 octopi kernel: [83764.132319] brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-84
Mar 23 08:39:45 octopi kernel: [83764.132350] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
Mar 23 08:39:45 octopi kernel: [83764.132396] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -84
Mar 23 08:39:45 octopi kernel: [83764.132567] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:45 octopi kernel: [83764.132842] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:45 octopi kernel: [83764.133140] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 08:39:45 octopi kernel: [83764.133313] brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-84
Mar 23 19:20:41 octopi kernel: [122220.767301] brcmfmac: brcmf_sdio_dpc: sdio ctrlframe tx failed err=-84
Mar 23 19:20:41 octopi kernel: [122220.767314] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation
Mar 23 19:20:41 octopi kernel: [122220.767329] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -84
Mar 23 19:20:41 octopi kernel: [122220.767338] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -84
Mar 23 19:20:48 octopi kernel: [122227.981278] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 19:20:51 octopi kernel: [122230.769413] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 19:20:51 octopi kernel: [122230.769538] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Mar 23 19:20:51 octopi kernel: [122230.769657] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame

@dwery
Copy link
Contributor

@dwery dwery commented Mar 28, 2021

Same issue with a raspberry pi 4 and
Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
and kernel 5.10.25-v8+

@morchaos
Copy link

@morchaos morchaos commented Apr 3, 2021

both Rpi4 and Rpi3 are seeing this issue now, and all software are up-to-date with "sudo apt upgrade"

[ 13.011868] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 13.249616] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 13.260818] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 13.286194] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[ 16.603610] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled

my kernel is

Linux RPi3-3 5.4.0-1032-raspi #35-Ubuntu SMP PREEMPT Fri Mar 19 20:56:57 UTC 2021 armv7l armv7l armv7l GNU/Linux

Best,
Jones

@wwebers
Copy link

@wwebers wwebers commented Apr 29, 2021

Very same issue here. Happened exactly after upgrading OctoPrint to version 1.6.0. Before everything worked fine.

kernel version 5.10.17-v7+

Another instance running OctoPrint 1.5.3 and kernel version 4.19.118-v7+ works fine without these errors.

@wwebers
Copy link

@wwebers wwebers commented Apr 30, 2021

Update: It's NOT a raspbian issue but a bug inside the latest OctoPrint plugin controlling the PSU via GPIO pins. This plugin itself contains an own GPIO plugin for compatibility reasons. But a bug inside that plugin breaks Wifi connections and produces all those error messages. Removing the GPIO plugin solves the problem.

@DaStivi
Copy link

@DaStivi DaStivi commented Apr 30, 2021

Removing the GPIO plugin solves the problem.

what todo? because i switched to klipper recently but still same octopi installation, just disabled all octoprint services (i think) and still getthe wifi outages after ah longer time of running...

and the pi also keeps reachable on wifi when using the firmware from "2016"

@dwery
Copy link
Contributor

@dwery dwery commented May 1, 2021

Update: It's NOT a raspbian issue but a bug inside the latest OctoPrint plugin controlling the PSU via GPIO pins. This plugin itself contains an own GPIO plugin for compatibility reasons. But a bug inside that plugin breaks Wifi connections and produces all those error messages. Removing the GPIO plugin solves the problem.

I don’t have that plug-in, the issue here is kernel related.

@foorschtbar
Copy link

@foorschtbar foorschtbar commented Jun 12, 2021

Same problem here. After some time with enabled webcam ( = a lot of traffic) the wifi connection is lost. Not every time, but most time. After reboot of the Pi its works without problem. I have two RPi 3B+ who works as OctoPrint printserver. One had no issues, but the other had. The working one had an older OctoPi Image. If i switch the Hardware + SD card, the problems keeps the same on one device, whats shows thats a software related problem. Update to latest versions and disable power management doesn't help

@ddacunha
Copy link

@ddacunha ddacunha commented Jun 13, 2021

I am unable to connect to the Pi 4 after reboot. It happens also intermittently after a successful connection. Cannot ping, connect via ssh or http to the Pi. The Pi is able to ping out and connect to outside services. Connection is restored when I restart sshd

# dmesg | grep "brcmfmac.*Firmware"
[    5.577091] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan  4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
# uname -a
Linux flsunq5 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l GNU/Linux

@yutayu
Copy link

@yutayu yutayu commented Jun 13, 2021

@ddacunha
pi@raspberrypi:~ $ dmesg | grep "brcmfmac.*Firmware"
[ 21.527059] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l GNU/Linux

I can use wifi , now. and here is no problem.

Edit
pi@raspberrypi:~ $ dmesg | grep brcmfmac
[ 20.927452] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 20.938426] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 20.939249] usbcore: registered new interface driver brcmfmac
[ 21.228414] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
[ 21.488163] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 21.527059] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e

Edit
In my case , closing port by iptables causes hostapd problem ( disassociated wifi ).
please see systemctl status hostapd when you feel wifi strange.

@ddacunha
Copy link

@ddacunha ddacunha commented Jun 14, 2021

You are correct, once I turned off power management in rc.local I have not encountered this issue

@foorschtbar
Copy link

@foorschtbar foorschtbar commented Jun 14, 2021

Same problem here. After some time with enabled webcam ( = a lot of traffic) the wifi connection is lost. Not every time, but most time. After reboot of the Pi its works without problem. I have two RPi 3B+ who works as OctoPrint printserver. One had no issues, but the other had. The working one had an older OctoPi Image. If i switch the Hardware + SD card, the problems keeps the same on one device, whats shows thats a software related problem. Update to latest versions and disable power management doesn't help

I downgraded the firmware to 7.45.154 (/lib/firmware/brcm - my older Pi had these files) and disabled power management. Now, after two days of 8h printing each and enabled webcam no problems. With 7.45.229 and also disabled power management it freezes. The firmware files were the only thing I changed. Also interesting is that the older Pi had no entry in rc.local, but dmesg says power management is disabled and the newer image says it is enabled.

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

Successfully merging a pull request may close this issue.

None yet