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 3/PiZeroW (Not 3B+) #1342

Open
dh-connect opened this Issue Mar 11, 2016 · 442 comments

Comments

Projects
None yet
@dh-connect

dh-connect commented Mar 11, 2016

I put the same sd card (running debian 8 jessie, kernel 4.1.19) from the raspberry pi 2 with usb wifi (EDIMAX EW-7811UN Wireless USB Adapter, 150 Mbit/s, IEEE802.11b/g/n) into the new raspberry pi 3 using integrated wlan. Since then the wlan freezes after while (several hours) of usage couldn't find out if it's due to havy wifi usage or not, because I haven't change the software I guess it has to do with the new hardware. When the wlan freezes the pi can't be reached any longer, neither ifdown + ifup nor restart networking service helps in this case, I have to reboot the system to get it back to work, syslog doesn't say much only this:
dhcpcd[522]: wlan0: fe80::8af7:c7ff:fece:5912: expired option 25,

I've tried to change these settings so far, but without improvement:

sudo nano /etc/network/interfaces
wireless-power off

sudo nano /etc/sysctl.conf
at the end of the file add the following line
vm.min_free_kbytes = 16384

sudo nano /boot/cmdline.txt
At the end of the line, add:
smsc95xx.turbo_mode=N
dwc_otg.dma_enable=1 dwc_otg.dma_burst_size=256

@clivem

This comment has been minimized.

Show comment
Hide comment
@clivem

clivem Mar 11, 2016

Contributor

EDIMAX EW-7811UN.... That's using rtl8188cus chipset, IIRC.

If you haven't already got one, create /etc/modprobe.d/8192cu.conf, with content....

Disable power management

options 8192cu rtw_power_mgnt=0 rtw_enusbss=0

Contributor

clivem commented Mar 11, 2016

EDIMAX EW-7811UN.... That's using rtl8188cus chipset, IIRC.

If you haven't already got one, create /etc/modprobe.d/8192cu.conf, with content....

Disable power management

options 8192cu rtw_power_mgnt=0 rtw_enusbss=0

@grbd

This comment has been minimized.

Show comment
Hide comment
@grbd

grbd Mar 11, 2016

The rpi3 actually uses the brcmfmac driver for the inbuilt wifi
there is an issue that requires the power saving / mangement to be turned off

I think the newer raspian kernels have patched this already to disable power saving by default but I don't think it's in this 4.5 branch yet

What I'm doing at the moment (gentoo install) is the following at bootup to disable the power saving on the wifi card

iw wlan0 set power_save off

grbd commented Mar 11, 2016

The rpi3 actually uses the brcmfmac driver for the inbuilt wifi
there is an issue that requires the power saving / mangement to be turned off

I think the newer raspian kernels have patched this already to disable power saving by default but I don't think it's in this 4.5 branch yet

What I'm doing at the moment (gentoo install) is the following at bootup to disable the power saving on the wifi card

iw wlan0 set power_save off

@clivem

This comment has been minimized.

Show comment
Hide comment
@clivem

clivem Mar 11, 2016

Contributor

The rpi3 actually uses the brcmfmac driver for the inbuilt wifi

Yes, I know. Oh I see. He's not using the EDIMAX EW-7811UN dongle anymore. He used to use it with RPi2.

Contributor

clivem commented Mar 11, 2016

The rpi3 actually uses the brcmfmac driver for the inbuilt wifi

Yes, I know. Oh I see. He's not using the EDIMAX EW-7811UN dongle anymore. He used to use it with RPi2.

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 11, 2016

yes I don't use the usb wifi any longer, how do I set up the cmd line to turn off the power management?
crontab
@reboot iw wlan0 set power_save off

dh-connect commented Mar 11, 2016

yes I don't use the usb wifi any longer, how do I set up the cmd line to turn off the power management?
crontab
@reboot iw wlan0 set power_save off

@grbd

This comment has been minimized.

Show comment
Hide comment
@grbd

grbd Mar 11, 2016

Not sure for raspian, since I'm using gentoo it'll be different

grbd commented Mar 11, 2016

Not sure for raspian, since I'm using gentoo it'll be different

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell
Contributor

pelwell commented Mar 11, 2016

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 14, 2016

Seems to work since I have turned the powermanagement off I haven't had another wlan crash.

dh-connect commented Mar 14, 2016

Seems to work since I have turned the powermanagement off I haven't had another wlan crash.

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 14, 2016

Just to mentioned it, to restart the wlan automatically after a crash, this here helps:
sudo cp /etc/wpa_supplicant/ifupdown.sh /etc/ifplugd/action.d/ifupdown

dh-connect commented Mar 14, 2016

Just to mentioned it, to restart the wlan automatically after a crash, this here helps:
sudo cp /etc/wpa_supplicant/ifupdown.sh /etc/ifplugd/action.d/ifupdown

@popcornmix

This comment has been minimized.

Show comment
Hide comment
@popcornmix

popcornmix Mar 14, 2016

Collaborator

BTW, latest apt-get upgrade kernel has power management disabled by default.
@dh-connect does this work for you if you remove your current workaround?

Collaborator

popcornmix commented Mar 14, 2016

BTW, latest apt-get upgrade kernel has power management disabled by default.
@dh-connect does this work for you if you remove your current workaround?

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 21, 2016

it's still crashing after the latest upgrade, now i get this error in syslog:
brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!

dh-connect commented Mar 21, 2016

it's still crashing after the latest upgrade, now i get this error in syslog:
brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Mar 21, 2016

Contributor

When you say it's crashing, are there symptoms other than the error message?

Contributor

pelwell commented Mar 21, 2016

When you say it's crashing, are there symptoms other than the error message?

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 21, 2016

no, just the one I have posted here but it is in the log many times

the wlan stops working, i can still work with it but to get the wlan back working I have to reboot it

dh-connect commented Mar 21, 2016

no, just the one I have posted here but it is in the log many times

the wlan stops working, i can still work with it but to get the wlan back working I have to reboot it

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Mar 21, 2016

Contributor

Thanks - I think "wlan stops working" counts as a symptom.

Contributor

pelwell commented Mar 21, 2016

Thanks - I think "wlan stops working" counts as a symptom.

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 21, 2016

I've tried a few things, but wlan still breaks down

to answer the question above when I take back the configuration
wireless-power off in /etc/network/interfaces
and reboot
and check the settings with iwconfig
the power management ist turned back on so by default I wouldn't say that this is diasbled so I will leave the configuration

I tried that with kernel 4.1.19 and now also with kernel 4.1.20 ... no change

when the wlan crashed and i try to turn it back on with ifdown and ifup wlan0 I get this:
Error for wireless request "Set Power Management" (8B2C) : SET failed on device wlan0 ; Invalid exchange.

I also got a few more error in syslog:

dhcpcd[532]: wlan0: xxx: expired option 25

Mar 21 17:29:35 raspberrypi kernel: [ 6627.337503] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -52
Mar 21 17:29:36 raspberrypi wpa_supplicant[6318]: Successfully initialized wpa_supplicant
Mar 21 17:29:36 raspberrypi dhcpcd[532]: wlan0: carrier lost

Mar 21 17:29:43 raspberrypi kernel: [ 6635.337616] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -52

Mar 21 17:29:45 raspberrypi kernel: [ 6637.337588] brcmfmac: brcmf_do_escan: error (-52)
Mar 21 17:29:45 raspberrypi kernel: [ 6637.337602] brcmfmac: brcmf_cfg80211_scan: scan error (-52)

Mar 21 17:29:47 raspberrypi kernel: [ 6639.337596] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -52
Mar 21 17:29:49 raspberrypi kernel: [ 6641.337632] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52

is there anything else I could try?

dh-connect commented Mar 21, 2016

I've tried a few things, but wlan still breaks down

to answer the question above when I take back the configuration
wireless-power off in /etc/network/interfaces
and reboot
and check the settings with iwconfig
the power management ist turned back on so by default I wouldn't say that this is diasbled so I will leave the configuration

I tried that with kernel 4.1.19 and now also with kernel 4.1.20 ... no change

when the wlan crashed and i try to turn it back on with ifdown and ifup wlan0 I get this:
Error for wireless request "Set Power Management" (8B2C) : SET failed on device wlan0 ; Invalid exchange.

I also got a few more error in syslog:

dhcpcd[532]: wlan0: xxx: expired option 25

Mar 21 17:29:35 raspberrypi kernel: [ 6627.337503] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -52
Mar 21 17:29:36 raspberrypi wpa_supplicant[6318]: Successfully initialized wpa_supplicant
Mar 21 17:29:36 raspberrypi dhcpcd[532]: wlan0: carrier lost

Mar 21 17:29:43 raspberrypi kernel: [ 6635.337616] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -52

Mar 21 17:29:45 raspberrypi kernel: [ 6637.337588] brcmfmac: brcmf_do_escan: error (-52)
Mar 21 17:29:45 raspberrypi kernel: [ 6637.337602] brcmfmac: brcmf_cfg80211_scan: scan error (-52)

Mar 21 17:29:47 raspberrypi kernel: [ 6639.337596] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -52
Mar 21 17:29:49 raspberrypi kernel: [ 6641.337632] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52

is there anything else I could try?

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 22, 2016

also these:

Mar 21 21:26:55 raspberrypi dhcpcd[526]: wlan0: xxx: expired option 25
Mar 21 21:28:54 raspberrypi kernel: [ 1958.899715] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
Mar 21 21:30:16 raspberrypi dhcpcd[526]: wlan0: xxx is unreachable, expiring it

dh-connect commented Mar 22, 2016

also these:

Mar 21 21:26:55 raspberrypi dhcpcd[526]: wlan0: xxx: expired option 25
Mar 21 21:28:54 raspberrypi kernel: [ 1958.899715] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
Mar 21 21:30:16 raspberrypi dhcpcd[526]: wlan0: xxx is unreachable, expiring it

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Mar 22, 2016

Contributor

I'm not surprised that iwconfig thinks the device has power-saving enabled - I blocked it within the driver itself, and either the state is saved in the higher layers or there is another change required in order to report it correctly. Either way, the evidence is strong that we have avoided the power-saving bugs, but some other problems still remain.

Do you have any rough figures for the time-to-failure and roughly how much data might have been transferred (from ifconfig)?

Contributor

pelwell commented Mar 22, 2016

I'm not surprised that iwconfig thinks the device has power-saving enabled - I blocked it within the driver itself, and either the state is saved in the higher layers or there is another change required in order to report it correctly. Either way, the evidence is strong that we have avoided the power-saving bugs, but some other problems still remain.

Do you have any rough figures for the time-to-failure and roughly how much data might have been transferred (from ifconfig)?

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 22, 2016

yes I do, when I have just the webserver running with not much traffic (less than 100 MB) it lasts a day or two, when i transfer large data files like 1 GB wlan crashes within 1 hour

dh-connect commented Mar 22, 2016

yes I do, when I have just the webserver running with not much traffic (less than 100 MB) it lasts a day or two, when i transfer large data files like 1 GB wlan crashes within 1 hour

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect Mar 29, 2016

anything I can provide to help to find the bug?

here are some error from syslog:

Mar 29 14:20:56 raspberrypi dhcpcd[535]: wlan0: xxx: expired option 25
Mar 29 14:30:15 raspberrypi dhcpcd[535]: wlan0: xxx is unreachable, expiring it
Mar 29 17:18:42 raspberrypi kernel: [186148.102420] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:43 raspberrypi kernel: [186149.101045] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:43 raspberrypi kernel: [186149.101145] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:44 raspberrypi kernel: [186150.101209] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:50 raspberrypi wpa_supplicant[478]: wlan0: CTRL-EVENT-DISCONNECTED bssid=xxx reason=3 locally_generated=1
Mar 29 17:18:50 raspberrypi kernel: [186156.181033] brcmfmac: brcmf_cfg80211_disconnect: error (-52)
Mar 29 17:18:52 raspberrypi kernel: [186158.181028] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:54 raspberrypi kernel: [186160.181046] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:56 raspberrypi kernel: [186162.181048] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:58 raspberrypi kernel: [186164.181049] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:58 raspberrypi kernel: [186164.185477] cfg80211: Calling CRDA to update world regulatory domain
Mar 29 17:18:58 raspberrypi dhcpcd[535]: wlan0: carrier lost
Mar 29 17:18:58 raspberrypi wpa_supplicant[7354]: Successfully initialized wpa_supplicant
Mar 29 17:18:58 raspberrypi kernel: [186164.314511] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
Mar 29 17:18:58 raspberrypi kernel: [186164.314541] cfg80211: World regulatory domain updated:
Mar 29 17:18:58 raspberrypi kernel: [186164.314548] cfg80211: DFS Master region: unset
Mar 29 17:18:58 raspberrypi kernel: [186164.314555] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Mar 29 17:18:58 raspberrypi kernel: [186164.314565] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314573] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314581] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314592] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314602] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Mar 29 17:18:58 raspberrypi kernel: [186164.314611] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Mar 29 17:18:58 raspberrypi kernel: [186164.314645] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314654] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

dh-connect commented Mar 29, 2016

anything I can provide to help to find the bug?

here are some error from syslog:

Mar 29 14:20:56 raspberrypi dhcpcd[535]: wlan0: xxx: expired option 25
Mar 29 14:30:15 raspberrypi dhcpcd[535]: wlan0: xxx is unreachable, expiring it
Mar 29 17:18:42 raspberrypi kernel: [186148.102420] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:43 raspberrypi kernel: [186149.101045] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:43 raspberrypi kernel: [186149.101145] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:44 raspberrypi kernel: [186150.101209] brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
Mar 29 17:18:50 raspberrypi wpa_supplicant[478]: wlan0: CTRL-EVENT-DISCONNECTED bssid=xxx reason=3 locally_generated=1
Mar 29 17:18:50 raspberrypi kernel: [186156.181033] brcmfmac: brcmf_cfg80211_disconnect: error (-52)
Mar 29 17:18:52 raspberrypi kernel: [186158.181028] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:54 raspberrypi kernel: [186160.181046] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:56 raspberrypi kernel: [186162.181048] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:58 raspberrypi kernel: [186164.181049] brcmfmac: send_key_to_dongle: wsec_key error (-52)
Mar 29 17:18:58 raspberrypi kernel: [186164.185477] cfg80211: Calling CRDA to update world regulatory domain
Mar 29 17:18:58 raspberrypi dhcpcd[535]: wlan0: carrier lost
Mar 29 17:18:58 raspberrypi wpa_supplicant[7354]: Successfully initialized wpa_supplicant
Mar 29 17:18:58 raspberrypi kernel: [186164.314511] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
Mar 29 17:18:58 raspberrypi kernel: [186164.314541] cfg80211: World regulatory domain updated:
Mar 29 17:18:58 raspberrypi kernel: [186164.314548] cfg80211: DFS Master region: unset
Mar 29 17:18:58 raspberrypi kernel: [186164.314555] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Mar 29 17:18:58 raspberrypi kernel: [186164.314565] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314573] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314581] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314592] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314602] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Mar 29 17:18:58 raspberrypi kernel: [186164.314611] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Mar 29 17:18:58 raspberrypi kernel: [186164.314645] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Mar 29 17:18:58 raspberrypi kernel: [186164.314654] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Mar 30, 2016

Contributor

Thanks for the offer, but this is in the hands of Broadcom now.

Contributor

pelwell commented Mar 30, 2016

Thanks for the offer, but this is in the hands of Broadcom now.

@juched78

This comment has been minimized.

Show comment
Hide comment
@juched78

juched78 May 5, 2016

Any update from Broadcom if this is a bug which will be fixed? I now have a cron job setup to bring down and up wlan0 when it fails to ping.

juched78 commented May 5, 2016

Any update from Broadcom if this is a bug which will be fixed? I now have a cron job setup to bring down and up wlan0 when it fails to ping.

@dh-connect

This comment has been minimized.

Show comment
Hide comment
@dh-connect

dh-connect May 5, 2016

quick update from my side, i could get the problem fixed seems to be driver related, i installed Ubuntu MATE 16.04 with kernel 4.4.8 and haven't had any problems with wifi since

i mean they advertise is: "Ubuntu MATE 16.04 also has fully working Bluetooth and Wifi on the Raspberry Pi 3" which seems true

maybe it also works with a new Debian release, which i can not tell

dh-connect commented May 5, 2016

quick update from my side, i could get the problem fixed seems to be driver related, i installed Ubuntu MATE 16.04 with kernel 4.4.8 and haven't had any problems with wifi since

i mean they advertise is: "Ubuntu MATE 16.04 also has fully working Bluetooth and Wifi on the Raspberry Pi 3" which seems true

maybe it also works with a new Debian release, which i can not tell

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell May 5, 2016

Contributor

@juched78 Are you running a 4.4 kernel? If not, please run sudo rpi-update to get the latest 4.4.8 build and see if that suffers the same problem.

The Broadcom drivers have changed significantly since 4.1, and our 4.4 tree includes back-ports of some fixes that went into 4.5. I'm not aware of any outstanding bugs apart from the failure to wake from sleep (power management is still disabled) - channels 12 & 13 are usable where permitted, and Ad Hoc mode doesn't crash - but there may still be lurking issues.

Contributor

pelwell commented May 5, 2016

@juched78 Are you running a 4.4 kernel? If not, please run sudo rpi-update to get the latest 4.4.8 build and see if that suffers the same problem.

The Broadcom drivers have changed significantly since 4.1, and our 4.4 tree includes back-ports of some fixes that went into 4.5. I'm not aware of any outstanding bugs apart from the failure to wake from sleep (power management is still disabled) - channels 12 & 13 are usable where permitted, and Ad Hoc mode doesn't crash - but there may still be lurking issues.

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell May 5, 2016

Contributor

Oh, there is one reported bug still in 4.4.8 - apparently heavy use of hostapd can lead to a kernel warning (see #1375).

Contributor

pelwell commented May 5, 2016

Oh, there is one reported bug still in 4.4.8 - apparently heavy use of hostapd can lead to a kernel warning (see #1375).

@juched78

This comment has been minimized.

Show comment
Hide comment
@juched78

juched78 May 5, 2016

I am running:
Linux XXX 4.4.8-v7+ #880 SMP Fri Apr 22 21:55:04 BST 2016 armv7l GNU/Linux

Apr 27 2016 11:06:18
Copyright (c) 2012 Broadcom
version 9b52ab7b475f4a056658fd2d95d2440b32167390 (clean) (release)

With my Netgear R7000 running Shibby Tomato, around 2 days in the wifi drops, and in the sys logs I see:

CTRL-EVENT-DISCONNECTED
brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-52)
brcmfmac: send_key_to_dongle: wsec_key error (-52)
...
brcmfmac: brcmf_do_escan: error (-52)
...
wpa_supplicant[506]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
...
brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code

(then I see it scan and re-pick my country code CA)

brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -52
brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -52

Then it seems to never reconnect...

Using sudo ifdown wlan0 followed by sudo ifup wlan0 brings back my connection.

juched78 commented May 5, 2016

I am running:
Linux XXX 4.4.8-v7+ #880 SMP Fri Apr 22 21:55:04 BST 2016 armv7l GNU/Linux

Apr 27 2016 11:06:18
Copyright (c) 2012 Broadcom
version 9b52ab7b475f4a056658fd2d95d2440b32167390 (clean) (release)

With my Netgear R7000 running Shibby Tomato, around 2 days in the wifi drops, and in the sys logs I see:

CTRL-EVENT-DISCONNECTED
brcmfmac: brcmf_link_down: WLC_DISASSOC failed (-52)
brcmfmac: send_key_to_dongle: wsec_key error (-52)
...
brcmfmac: brcmf_do_escan: error (-52)
...
wpa_supplicant[506]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
...
brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code

(then I see it scan and re-pick my country code CA)

brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -52
brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52
brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -52

Then it seems to never reconnect...

Using sudo ifdown wlan0 followed by sudo ifup wlan0 brings back my connection.

@juched78

This comment has been minimized.

Show comment
Hide comment
@juched78

juched78 May 5, 2016

Just upgraded to:
Linux JuchePi 4.4.8-v7+ #881 SMP Sat Apr 30 12:16:50 BST 2016 armv7l GNU/Linux

Not sure what is all different from the 22nd to the 30th. I will monitor the connection.

juched78 commented May 5, 2016

Just upgraded to:
Linux JuchePi 4.4.8-v7+ #881 SMP Sat Apr 30 12:16:50 BST 2016 armv7l GNU/Linux

Not sure what is all different from the 22nd to the 30th. I will monitor the connection.

@maciex

This comment has been minimized.

Show comment
Hide comment
@maciex

maciex May 9, 2016

My RPi 3 also hit that problem. I got few different kernel messages. Mainly one of those below.
After that I can' get the WiFi working, bringing wlan0 down then up does not help.

May 09 21:24:25 osmc kernel: brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
May 09 22:00:15 osmc kernel: brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
May 09 22:00:18 osmc kernel: brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
May 10 00:51:10 osmc kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-52)
May 10 00:51:12 osmc kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
May 10 00:53:16 osmc kernel: brcmfmac: brcmf_do_escan: error (-52)
May 10 00:53:16 osmc kernel: brcmfmac: brcmf_cfg80211_scan: scan error (-52)

Raspberry is powered from original power adapter for version 3. I'm running latest OSMC:
$ uname -a
Linux osmc 4.4.8-3-osmc #1 SMP PREEMPT Sun May 1 18:57:43 UTC 2016 armv7l GNU/Linux

maciex commented May 9, 2016

My RPi 3 also hit that problem. I got few different kernel messages. Mainly one of those below.
After that I can' get the WiFi working, bringing wlan0 down then up does not help.

May 09 21:24:25 osmc kernel: brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
May 09 22:00:15 osmc kernel: brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
May 09 22:00:18 osmc kernel: brcmfmac: brcmf_sdio_bus_txdata: out of bus->txq !!!
May 10 00:51:10 osmc kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-52)
May 10 00:51:12 osmc kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
May 10 00:53:16 osmc kernel: brcmfmac: brcmf_do_escan: error (-52)
May 10 00:53:16 osmc kernel: brcmfmac: brcmf_cfg80211_scan: scan error (-52)

Raspberry is powered from original power adapter for version 3. I'm running latest OSMC:
$ uname -a
Linux osmc 4.4.8-3-osmc #1 SMP PREEMPT Sun May 1 18:57:43 UTC 2016 armv7l GNU/Linux

@juched78

This comment has been minimized.

Show comment
Hide comment
@juched78

juched78 May 11, 2016

Still monitoring. I had openhab go offline after running 3 days but for some reason I could still ssh into the Pi which I usually couldn't. The top of the hour and the wifi script ran to bring down and bring up the connection and then it reconnected to my openhab org. Odd. Will keep watching.

juched78 commented May 11, 2016

Still monitoring. I had openhab go offline after running 3 days but for some reason I could still ssh into the Pi which I usually couldn't. The top of the hour and the wifi script ran to bring down and bring up the connection and then it reconnected to my openhab org. Odd. Will keep watching.

@duncanmcdowell

This comment has been minimized.

Show comment
Hide comment
@duncanmcdowell

duncanmcdowell May 14, 2016

I am also experiencing the same issue - dmesg trace as follows:

send_key_to_dongle: wsec_key error (-52)
brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -52
brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
brcmf_cfg80211_get_tx_power: error (-52)

Usage:

rp3 is being used as a router/access point

Connectivity length seems random - I've had as high as two weeks, and as bad as a few minutes. Lately it's been going out every 20 minutes or so. Bringing wlan0 down and back up does not resolve the issue - a full reboot is required.

Problem seems to be exacerbated while streaming Netflix from my AppleTV. Though this was not the case when I had the two weeks of uptime.

I'm on 4.4.10-v7+

duncanmcdowell commented May 14, 2016

I am also experiencing the same issue - dmesg trace as follows:

send_key_to_dongle: wsec_key error (-52)
brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -52
brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
brcmf_cfg80211_get_tx_power: error (-52)

Usage:

rp3 is being used as a router/access point

Connectivity length seems random - I've had as high as two weeks, and as bad as a few minutes. Lately it's been going out every 20 minutes or so. Bringing wlan0 down and back up does not resolve the issue - a full reboot is required.

Problem seems to be exacerbated while streaming Netflix from my AppleTV. Though this was not the case when I had the two weeks of uptime.

I'm on 4.4.10-v7+

@maciex

This comment has been minimized.

Show comment
Hide comment
@maciex

maciex May 15, 2016

I switched the channel from 13 to 6 to check if that could be the problem (there were some defects about the high channels) and since then I haven't had a WiFi freez. But that could be a coincidence...

maciex commented May 15, 2016

I switched the channel from 13 to 6 to check if that could be the problem (there were some defects about the high channels) and since then I haven't had a WiFi freez. But that could be a coincidence...

@maciex

This comment has been minimized.

Show comment
Hide comment
@maciex

maciex May 16, 2016

Changing access point channels didn't help. WiFi still breaks. Last few times I had to restart few times in a row to get it working.

maciex commented May 16, 2016

Changing access point channels didn't help. WiFi still breaks. Last few times I had to restart few times in a row to get it working.

@loganwendholt

This comment has been minimized.

Show comment
Hide comment
@loganwendholt

loganwendholt May 29, 2016

I experience this issue specifically when I try to do an SFTP transfer between the rpi3 and my Galaxy S5 phone. When I try to perform the same transfer from my laptop, everything runs smoothly.

Running latest kernel from rpi-update:

Linux raspberrypi 4.4.11-v7+ #888 SMP Mon May 23 20:10:33 BST 2016 armv7l GNU/Linux

Error message from syslog:

May 29 18:10:46 raspberrypi kernel: [  178.605907] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012

It seems that the only solution after this error is a reboot.

loganwendholt commented May 29, 2016

I experience this issue specifically when I try to do an SFTP transfer between the rpi3 and my Galaxy S5 phone. When I try to perform the same transfer from my laptop, everything runs smoothly.

Running latest kernel from rpi-update:

Linux raspberrypi 4.4.11-v7+ #888 SMP Mon May 23 20:10:33 BST 2016 armv7l GNU/Linux

Error message from syslog:

May 29 18:10:46 raspberrypi kernel: [  178.605907] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012

It seems that the only solution after this error is a reboot.

@juched78

This comment has been minimized.

Show comment
Hide comment
@juched78

juched78 Jul 5, 2016

I have had mine drop off the network twice in the past week. First time I was in a rush so just unplugged and rebooted. Few days later it happened again, rebooted again and then ran full system updates (including firmware) and will monitor. Have it mounted with no monitor near by, so getting details on the error needs more effort :)

juched78 commented Jul 5, 2016

I have had mine drop off the network twice in the past week. First time I was in a rush so just unplugged and rebooted. Few days later it happened again, rebooted again and then ran full system updates (including firmware) and will monitor. Have it mounted with no monitor near by, so getting details on the error needs more effort :)

@xtecox

This comment has been minimized.

Show comment
Hide comment
@xtecox

xtecox Jul 6, 2016

Same problem here. It always freeze when transfer big files by sftp. Just rebooting to solve

xtecox commented Jul 6, 2016

Same problem here. It always freeze when transfer big files by sftp. Just rebooting to solve

@BenoitSvB

This comment has been minimized.

Show comment
Hide comment
@BenoitSvB

BenoitSvB Jul 8, 2016

This issue maybe related to #1313

BenoitSvB commented Jul 8, 2016

This issue maybe related to #1313

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Jul 12, 2016

Contributor

Broadcom say that #1313 is a non-issue, and the latest kernel no longer shows those messages.

I've been unable to reproduce this problem. Has anybody been able to capture a packet trace around the time of failure?

Contributor

pelwell commented Jul 12, 2016

Broadcom say that #1313 is a non-issue, and the latest kernel no longer shows those messages.

I've been unable to reproduce this problem. Has anybody been able to capture a packet trace around the time of failure?

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Jul 13, 2016

Contributor

If anyone has time to do some more testing with a debug-enabled driver module it would be much appreciated:

  1. Run sudo rpi-update and reboot. This is to get your kernel up to the same level as mine so that the module is compatible.

  2. Download and install the updated driver module:

BRCM80211=/lib/modules/`uname -r`/kernel/drivers/net/wireless/brcm80211
BRCMFMAC=$BRCM80211/brcmfmac
wget -O brcmfmac.ko "https://docs.google.com/uc?authuser=0&id=0B8VsfKAD4-NOR1ZxWS00ZmFrR1k&export=download"
wget -O brcmutil.ko "https://docs.google.com/uc?authuser=0&id=0B8VsfKAD4-NOM0ZDd3FvYUNwZXc&export=download"
sudo mv $BRCMFMAC/brcmfmac.ko{,.orig}
sudo cp brcmfmac.ko $BRCMFMAC
sudo sh -c "echo options brcmfmac debug=0x100000 > /etc/modprobe.d/brcmfmac.conf"
BRCMUTIL=$BRCM80211/brcmutil
sudo mv $BRCMUTIL/brcmutil.ko{,.orig}
sudo cp brcmutil.ko $BRCMUTIL/brcmutil.ko

Reboot to activate the new modules.

  1. Use your Pi as normal, then if your WiFi freezes run:
dmesg > wifi_freeze.txt

and upload it to your favourite pasting site (or create a Gist). One or two logs should be plenty.

To restore the original version of the module:

BRCM80211=/lib/modules/`uname -r`/kernel/drivers/net/wireless/brcm80211
sudo mv $BRCM80211/brcmfmac/brcmfmac.ko{.orig,}
sudo mv $BRCM80211/brcmutil/brcmutil.ko{.orig,}

Thanks in advance.

Contributor

pelwell commented Jul 13, 2016

If anyone has time to do some more testing with a debug-enabled driver module it would be much appreciated:

  1. Run sudo rpi-update and reboot. This is to get your kernel up to the same level as mine so that the module is compatible.

  2. Download and install the updated driver module:

BRCM80211=/lib/modules/`uname -r`/kernel/drivers/net/wireless/brcm80211
BRCMFMAC=$BRCM80211/brcmfmac
wget -O brcmfmac.ko "https://docs.google.com/uc?authuser=0&id=0B8VsfKAD4-NOR1ZxWS00ZmFrR1k&export=download"
wget -O brcmutil.ko "https://docs.google.com/uc?authuser=0&id=0B8VsfKAD4-NOM0ZDd3FvYUNwZXc&export=download"
sudo mv $BRCMFMAC/brcmfmac.ko{,.orig}
sudo cp brcmfmac.ko $BRCMFMAC
sudo sh -c "echo options brcmfmac debug=0x100000 > /etc/modprobe.d/brcmfmac.conf"
BRCMUTIL=$BRCM80211/brcmutil
sudo mv $BRCMUTIL/brcmutil.ko{,.orig}
sudo cp brcmutil.ko $BRCMUTIL/brcmutil.ko

Reboot to activate the new modules.

  1. Use your Pi as normal, then if your WiFi freezes run:
dmesg > wifi_freeze.txt

and upload it to your favourite pasting site (or create a Gist). One or two logs should be plenty.

To restore the original version of the module:

BRCM80211=/lib/modules/`uname -r`/kernel/drivers/net/wireless/brcm80211
sudo mv $BRCM80211/brcmfmac/brcmfmac.ko{.orig,}
sudo mv $BRCM80211/brcmutil/brcmutil.ko{.orig,}

Thanks in advance.

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Jul 13, 2016

Contributor

Hang on for a moment while we verify that the debug output really is enabled.

Contributor

pelwell commented Jul 13, 2016

Hang on for a moment while we verify that the debug output really is enabled.

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Jul 13, 2016

Contributor

You will also need to enable a debug feature on the driver:

sudo sh -c "echo options brcmfmac debug=0x100000 > /etc/modprobe.d/brcmfmac.conf"

I've amended the instructions above.

After a reboot your dmesg output should include something like this:

[   10.848903] brcmfmac: CONSOLE: hndarm_armr addr: 0x18003000, cr4_idx: 0
[   10.860475] brcmfmac: CONSOLE: 000000.001
[   10.869471] brcmfmac: CONSOLE: RTE (SDIO-CDC) 7.45.41.26 (r640327) on BCM43430 r1 @ 37.4/81.6/81.6MHz
[   10.883644] brcmfmac: CONSOLE: 000000.001 sdpcmdcdc0: Broadcom SDPCMD CDC driver
[   10.896090] brcmfmac: CONSOLE: 000000.005 reclaim section 0: Returned 47716 bytes to the heap
[   10.909734] brcmfmac: CONSOLE: 000000.007 wlc_bmac_info_init: host_enab 1
[   10.921417] brcmfmac: CONSOLE: 000000.026 wl0: Broadcom BCM43430 802.11 Wireless Controller 7.45.41.26 (r640327)
[   10.936777] brcmfmac: CONSOLE: 000000.027 TCAM: 256 used: 179 exceed:0
[   10.936794] brcmfmac: CONSOLE: 000000.028 reclaim section 1: Returned 81268 bytes to the heap
[   10.936803] brcmfmac: CONSOLE: 000000.029 sdpcmd_dpc: Enable
[   10.938242] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[   10.949404] brcmfmac: CONSOLE: 000000.125 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[   10.963663] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[   10.969865] brcmfmac: CONSOLE: 000000.150 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[   10.969876] brcmfmac: CONSOLE: 000000.151 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[   11.189639] brcmfmac: CONSOLE: 000000.368 wl0: wl_open
Contributor

pelwell commented Jul 13, 2016

You will also need to enable a debug feature on the driver:

sudo sh -c "echo options brcmfmac debug=0x100000 > /etc/modprobe.d/brcmfmac.conf"

I've amended the instructions above.

After a reboot your dmesg output should include something like this:

[   10.848903] brcmfmac: CONSOLE: hndarm_armr addr: 0x18003000, cr4_idx: 0
[   10.860475] brcmfmac: CONSOLE: 000000.001
[   10.869471] brcmfmac: CONSOLE: RTE (SDIO-CDC) 7.45.41.26 (r640327) on BCM43430 r1 @ 37.4/81.6/81.6MHz
[   10.883644] brcmfmac: CONSOLE: 000000.001 sdpcmdcdc0: Broadcom SDPCMD CDC driver
[   10.896090] brcmfmac: CONSOLE: 000000.005 reclaim section 0: Returned 47716 bytes to the heap
[   10.909734] brcmfmac: CONSOLE: 000000.007 wlc_bmac_info_init: host_enab 1
[   10.921417] brcmfmac: CONSOLE: 000000.026 wl0: Broadcom BCM43430 802.11 Wireless Controller 7.45.41.26 (r640327)
[   10.936777] brcmfmac: CONSOLE: 000000.027 TCAM: 256 used: 179 exceed:0
[   10.936794] brcmfmac: CONSOLE: 000000.028 reclaim section 1: Returned 81268 bytes to the heap
[   10.936803] brcmfmac: CONSOLE: 000000.029 sdpcmd_dpc: Enable
[   10.938242] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[   10.949404] brcmfmac: CONSOLE: 000000.125 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[   10.963663] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[   10.969865] brcmfmac: CONSOLE: 000000.150 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[   10.969876] brcmfmac: CONSOLE: 000000.151 wl0: wlc_enable_probe_req: state down, deferring setting of host flags
[   11.189639] brcmfmac: CONSOLE: 000000.368 wl0: wl_open
@BenoitSvB

This comment has been minimized.

Show comment
Hide comment
@BenoitSvB

BenoitSvB Jul 13, 2016

@pelwell after executing your instructions I no longer have wifi...

root@pi3b:/home/pi# dmesg | grep brcmf
[ 15.582665] brcmfmac: Unknown symbol brcmu_dbg_hex_dump (err 0)
[ 15.613709] brcmfmac: Unknown symbol brcmu_dbg_hex_dump (err 0)

BenoitSvB commented Jul 13, 2016

@pelwell after executing your instructions I no longer have wifi...

root@pi3b:/home/pi# dmesg | grep brcmf
[ 15.582665] brcmfmac: Unknown symbol brcmu_dbg_hex_dump (err 0)
[ 15.613709] brcmfmac: Unknown symbol brcmu_dbg_hex_dump (err 0)

popcornmix added a commit that referenced this issue Apr 3, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.

raspbian-autopush pushed a commit to raspbian-packages/linux-4.9 that referenced this issue Apr 7, 2018

Debian Kernel Team Raspbian forward porter
rpi_1327_3eb9b34b584747e93e8c13e4126a0dd18189cec1
commit 3eb9b34
Author: James Hughes <james.hughes@raspberrypi.org>
Date:   Fri Jul 21 09:55:12 2017 +0100

    Sets the BCDC priority to constant 0
    
    This is to workaround for a possible issue in the
    wireless chip firmware where some packets with
    higher priorities seem to go missing.
    
    See raspberrypi/linux#1342 for
    details.


Gbp-Pq: Topic rpi
Gbp-Pq: Name rpi_1327_3eb9b34b584747e93e8c13e4126a0dd18189cec1.patch

popcornmix added a commit that referenced this issue Apr 9, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.

popcornmix added a commit that referenced this issue Apr 9, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.

popcornmix added a commit that referenced this issue Apr 16, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.

popcornmix added a commit that referenced this issue Apr 16, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.
@JamesH65

This comment has been minimized.

Show comment
Hide comment
@JamesH65

JamesH65 Apr 23, 2018

Contributor

Does anyone subscribed to this issue, running the 3B (not plus), still see the problems with the latest firmware and kernel? Would like any reports of continuing failure - last posts on subject above seem to imply things are now working OK.

Contributor

JamesH65 commented Apr 23, 2018

Does anyone subscribed to this issue, running the 3B (not plus), still see the problems with the latest firmware and kernel? Would like any reports of continuing failure - last posts on subject above seem to imply things are now working OK.

@RipperFox

This comment has been minimized.

Show comment
Hide comment
@RipperFox

RipperFox Apr 23, 2018

My 3B's up since 44 days with this:

Linux rpi3 4.14.24-v7+ #1097 SMP Mon Mar 5 16:42:05 GMT 2018
brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f

No problems since then..

RipperFox commented Apr 23, 2018

My 3B's up since 44 days with this:

Linux rpi3 4.14.24-v7+ #1097 SMP Mon Mar 5 16:42:05 GMT 2018
brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f

No problems since then..

@JamesH65

This comment has been minimized.

Show comment
Hide comment
@JamesH65

JamesH65 Apr 23, 2018

Contributor

Good news. Unless I hear otherwise, I'll probably close this thread in a week or two, although it can be reopened at any time if problems reoccur.

Contributor

JamesH65 commented Apr 23, 2018

Good news. Unless I hear otherwise, I'll probably close this thread in a week or two, although it can be reopened at any time if problems reoccur.

@henr2011

This comment has been minimized.

Show comment
Hide comment
@henr2011

henr2011 Apr 25, 2018

I started having this issue about a week ago, having not heard of it before then. I also use the pi most often with a samsung phone as router - mine is an s4. I am writing this connected direct to the s4 with usb, ie using rndis. Here are my details from today's boot:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
thenry@pi3portable:~ $ dmesg | grep brcmfmac
[ 9.965782] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 9.972059] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 9.972250] usbcore: registered new interface driver brcmfmac
[ 10.147562] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 10.148507] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
[ 18.538641] brcmfmac: power management disabled
[ 30.629545] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
[ 33.191450] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 33.194850] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 35.751496] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 35.754898] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 35.754906] brcmfmac: brcmf_pno_clean: failed code -110
[ 43.271438] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 43.274800] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 43.274807] brcmfmac: brcmf_do_escan: error (-110)
[ 43.274811] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[ 7673.758073] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 7673.761437] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 7673.761454] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[ 7676.328075] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 7676.331449] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 7676.331466] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
[ 7678.878084] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 7678.881460] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 7681.448101] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
[ 7689.118098] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 7689.118241] brcmfmac: power management disabled
[ 7691.678100] brcmfmac: brcmf_cfg80211_set_power_mgmt: error (-110)
[ 7694.238122] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[ 7696.798118] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
[ 7699.358158] brcmfmac: brcmf_do_escan: error (-110)
[ 7699.358167] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[ 7701.918127] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
[11406.881341] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[11406.881352] brcmfmac: brcmf_cfg80211_reg_notifier: Country code iovar returned err = -110
[11579.921479] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[11582.491485] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
[11587.611478] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
thenry@pi3portable:~ $
thenry@pi3portable:~ $ uname -a
Linux pi3portable 4.14.27-v7+ #1100 SMP Fri Mar 16 13:51:48 GMT 2018 armv7l GNU/Linux
thenry@pi3portable:~ $
I am running this kernel because I changed to the next stream when I was testing booting from usb, and didn't change back afterwards. Then I got the notice about the new kernel (4.14) so decided to try that, about a month ago. It has been fine, no problems until this one. Only other major change is I switched from NetworkManager to systemd-networkd several days ago but that is after this problem first showed itself.
Regards,
Trevor Henry

henr2011 commented Apr 25, 2018

I started having this issue about a week ago, having not heard of it before then. I also use the pi most often with a samsung phone as router - mine is an s4. I am writing this connected direct to the s4 with usb, ie using rndis. Here are my details from today's boot:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
thenry@pi3portable:~ $ dmesg | grep brcmfmac
[ 9.965782] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 9.972059] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 9.972250] usbcore: registered new interface driver brcmfmac
[ 10.147562] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 10.148507] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
[ 18.538641] brcmfmac: power management disabled
[ 30.629545] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
[ 33.191450] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 33.194850] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 35.751496] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 35.754898] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 35.754906] brcmfmac: brcmf_pno_clean: failed code -110
[ 43.271438] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 43.274800] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 43.274807] brcmfmac: brcmf_do_escan: error (-110)
[ 43.274811] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[ 7673.758073] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 7673.761437] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 7673.761454] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[ 7676.328075] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 7676.331449] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 7676.331466] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
[ 7678.878084] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 7678.881460] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 7681.448101] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
[ 7689.118098] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 7689.118241] brcmfmac: power management disabled
[ 7691.678100] brcmfmac: brcmf_cfg80211_set_power_mgmt: error (-110)
[ 7694.238122] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[ 7696.798118] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
[ 7699.358158] brcmfmac: brcmf_do_escan: error (-110)
[ 7699.358167] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
[ 7701.918127] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
[11406.881341] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[11406.881352] brcmfmac: brcmf_cfg80211_reg_notifier: Country code iovar returned err = -110
[11579.921479] brcmfmac: _brcmf_set_multicast_list: Setting mcast_list failed, -110
[11582.491485] brcmfmac: _brcmf_set_multicast_list: Setting allmulti failed, -110
[11587.611478] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -110
thenry@pi3portable:~ $
thenry@pi3portable:~ $ uname -a
Linux pi3portable 4.14.27-v7+ #1100 SMP Fri Mar 16 13:51:48 GMT 2018 armv7l GNU/Linux
thenry@pi3portable:~ $
I am running this kernel because I changed to the next stream when I was testing booting from usb, and didn't change back afterwards. Then I got the notice about the new kernel (4.14) so decided to try that, about a month ago. It has been fine, no problems until this one. Only other major change is I switched from NetworkManager to systemd-networkd several days ago but that is after this problem first showed itself.
Regards,
Trevor Henry

@henr2011

This comment has been minimized.

Show comment
Hide comment
@henr2011

henr2011 Apr 26, 2018

Update:
After I read all the related posts I found the latest firmware in the post https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=203508
and this fixed my problem.

test version of brcmfmas43430-sdio.bin installed 250418

version 7.45.98.38 Oct 23 2017, replaced version 7.45.41.46 Aug 7 2017

before:

[ 10.368086] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 10.376702] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 10.377026] usbcore: registered new interface driver brcmfmac
[ 10.599523] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 10.600577] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
[ 126.642710] brcmfmac: power management disabled
[ 139.249230] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
[ 141.751545] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 141.754973] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 144.311482] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 144.314959] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 144.314975] brcmfmac: brcmf_pno_clean: failed code -110
[ 151.831564] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 151.835066] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 151.835079] brcmfmac: brcmf_do_escan: error (-110)
[ 151.835084] brcmfmac: brcmf_cfg80211_scan: scan error (-110)

after:

thenry@pi3portable:~ $ dmesg | grep brcm
[ 10.115833] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 10.134926] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 10.135115] usbcore: registered new interface driver brcmfmac
[ 10.367703] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[ 10.368419] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14
[ 18.045308] brcmfmac: power management disabled
thenry@pi3portable:~ $

It has continued to work through several boots and I am now using it, connected by wifi to samsung s4 phone.
Thanks for your help, regards, Trevor Henry.

henr2011 commented Apr 26, 2018

Update:
After I read all the related posts I found the latest firmware in the post https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=203508
and this fixed my problem.

test version of brcmfmas43430-sdio.bin installed 250418

version 7.45.98.38 Oct 23 2017, replaced version 7.45.41.46 Aug 7 2017

before:

[ 10.368086] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 10.376702] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 10.377026] usbcore: registered new interface driver brcmfmac
[ 10.599523] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 10.600577] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47
[ 126.642710] brcmfmac: power management disabled
[ 139.249230] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
[ 141.751545] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 141.754973] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 144.311482] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 144.314959] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 144.314975] brcmfmac: brcmf_pno_clean: failed code -110
[ 151.831564] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 151.835066] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 151.835079] brcmfmac: brcmf_do_escan: error (-110)
[ 151.835084] brcmfmac: brcmf_cfg80211_scan: scan error (-110)

after:

thenry@pi3portable:~ $ dmesg | grep brcm
[ 10.115833] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 10.134926] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[ 10.135115] usbcore: registered new interface driver brcmfmac
[ 10.367703] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[ 10.368419] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14
[ 18.045308] brcmfmac: power management disabled
thenry@pi3portable:~ $

It has continued to work through several boots and I am now using it, connected by wifi to samsung s4 phone.
Thanks for your help, regards, Trevor Henry.

@JamesH65

This comment has been minimized.

Show comment
Hide comment
@JamesH65

JamesH65 Apr 26, 2018

Contributor

I thought the latest firmware was already in the latest images, so would have expected that an upgrade to 4.14 would have brought the latest firmware in. Did you build you own kernel?

Contributor

JamesH65 commented Apr 26, 2018

I thought the latest firmware was already in the latest images, so would have expected that an upgrade to 4.14 would have brought the latest firmware in. Did you build you own kernel?

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Apr 26, 2018

Contributor

Yes - the current Raspbian images have firmware 7.45.98.38 from Oct 23 2017.

Contributor

pelwell commented Apr 26, 2018

Yes - the current Raspbian images have firmware 7.45.98.38 from Oct 23 2017.

popcornmix added a commit that referenced this issue Apr 26, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.
@henr2011

This comment has been minimized.

Show comment
Hide comment
@henr2011

henr2011 Apr 27, 2018

Hi, no I didn't build the kernel, I upgraded with rpi-update, and as you can see it was still running the Aug 2017 firmware after the update.

henr2011 commented Apr 27, 2018

Hi, no I didn't build the kernel, I upgraded with rpi-update, and as you can see it was still running the Aug 2017 firmware after the update.

@pelwell

This comment has been minimized.

Show comment
Hide comment
@pelwell

pelwell Apr 27, 2018

Contributor

rpi-update only upgrades the kernel, firmware and a small number of VideoCore-specific utilities. To upgrade everything, including the WiFi firmware, you must use apt-get upgrade/distupgrade.

Contributor

pelwell commented Apr 27, 2018

rpi-update only upgrades the kernel, firmware and a small number of VideoCore-specific utilities. To upgrade everything, including the WiFi firmware, you must use apt-get upgrade/distupgrade.

rsalveti added a commit to OpenSourceFoundries/linux that referenced this issue Apr 27, 2018

[OSF temphack] Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See raspberrypi/linux#1342 for
details.

Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>

popcornmix added a commit that referenced this issue May 5, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.

popcornmix added a commit that referenced this issue May 5, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.
@GitPickel

This comment has been minimized.

Show comment
Hide comment
@GitPickel

GitPickel May 14, 2018

Hi,
So i have this issue and it is better with the latest FW, 7.45.98.38, than it was but I still have problems.
Observations
If I boot the raspberry without doing anything then the WLAN comes up as it should.
If I try to use the bluetooth keyboard or mouse before the WLAN is up then the problem persists, i get no connection.
If I have a connection and disable/enable wireless network then the WLAN does not connect.
If i leave the WLAN on over night then the connection stops working.
I have three identical setups and the behaviour is the same on all of them.
Do not know if it matters but we are using WPA2 enterprise, PEAP and MSCHAPv2

GitPickel commented May 14, 2018

Hi,
So i have this issue and it is better with the latest FW, 7.45.98.38, than it was but I still have problems.
Observations
If I boot the raspberry without doing anything then the WLAN comes up as it should.
If I try to use the bluetooth keyboard or mouse before the WLAN is up then the problem persists, i get no connection.
If I have a connection and disable/enable wireless network then the WLAN does not connect.
If i leave the WLAN on over night then the connection stops working.
I have three identical setups and the behaviour is the same on all of them.
Do not know if it matters but we are using WPA2 enterprise, PEAP and MSCHAPv2

@JamesH65

This comment has been minimized.

Show comment
Hide comment
@JamesH65

JamesH65 May 14, 2018

Contributor

Do these issues only happen when the the BT devices are connected?

Contributor

JamesH65 commented May 14, 2018

Do these issues only happen when the the BT devices are connected?

@GitPickel

This comment has been minimized.

Show comment
Hide comment
@GitPickel

GitPickel May 14, 2018

Yes! Disabled bluetooth and connected usb keyboards and mouse and the WLAN connected faster than i have ever seen before.

GitPickel commented May 14, 2018

Yes! Disabled bluetooth and connected usb keyboards and mouse and the WLAN connected faster than i have ever seen before.

@JamesH65

This comment has been minimized.

Show comment
Hide comment
@JamesH65

JamesH65 May 14, 2018

Contributor

Still some issues with coexist then. Will need to be flagged up to Cypress I guess.

Just to check, you are using the latest Raspbian? Or something pretty new?

@pelwell ping

Contributor

JamesH65 commented May 14, 2018

Still some issues with coexist then. Will need to be flagged up to Cypress I guess.

Just to check, you are using the latest Raspbian? Or something pretty new?

@pelwell ping

@GitPickel

This comment has been minimized.

Show comment
Hide comment
@GitPickel

GitPickel May 14, 2018

Description: Raspbian GNU/Linux 9.4 (stretch)
Do you need any more info?

It hangs after :
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected

see log snip below

May 14 15:43:58 hwlab1_gul_rpi NetworkManager[2745]: [1526305438.7887] device (wlan0): supplicant interface state: disconnected -> associating
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: Associated with 44:d9:e7:f7:d5:34
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
May 14 15:43:58 hwlab1_gul_rpi NetworkManager[2745]: [1526305438.9263] device (wlan0): supplicant interface state: associating -> associated
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0716] device (wlan0): Activation: (wifi) association took too long
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0718] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
May 14 15:44:24 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-DISCONNECTED bssid=44:d9:e7:f7:d5:34 reason=3 locally_generated=1
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0937] device (wlan0): Activation: (wifi) asking for new secrets
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0959] sup-iface[0x1c438c0,wlan0]: connection disconnected (reason -3)

GitPickel commented May 14, 2018

Description: Raspbian GNU/Linux 9.4 (stretch)
Do you need any more info?

It hangs after :
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected

see log snip below

May 14 15:43:58 hwlab1_gul_rpi NetworkManager[2745]: [1526305438.7887] device (wlan0): supplicant interface state: disconnected -> associating
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: Associated with 44:d9:e7:f7:d5:34
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
May 14 15:43:58 hwlab1_gul_rpi NetworkManager[2745]: [1526305438.9263] device (wlan0): supplicant interface state: associating -> associated
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
May 14 15:43:58 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0716] device (wlan0): Activation: (wifi) association took too long
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0718] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
May 14 15:44:24 hwlab1_gul_rpi wpa_supplicant[445]: wlan0: CTRL-EVENT-DISCONNECTED bssid=44:d9:e7:f7:d5:34 reason=3 locally_generated=1
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0937] device (wlan0): Activation: (wifi) asking for new secrets
May 14 15:44:24 hwlab1_gul_rpi NetworkManager[2745]: [1526305464.0959] sup-iface[0x1c438c0,wlan0]: connection disconnected (reason -3)

popcornmix added a commit that referenced this issue May 17, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See #1342 for
details.
@DEvil0000

This comment has been minimized.

Show comment
Hide comment
@DEvil0000

DEvil0000 Jun 4, 2018

I have the same issue with octoPi 0.14 (every package updated, rpi firmware at latest, every octoprint plugin updated).

brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110

with this setup its 100% reproducable. Accassing the octoprint website on the pi (first time access after boot) from my samsung s4 active (android 5.0.1, using chrome) or from my samsung tablet 10inch note thing with also android 5.x i guess and chrome kills the wifi when the page is half loaded.
No cable connected to my Pi3, wifi on channel 11 with wpa2.
I tried disabling wifi power thing and switching to wifi channel 6 without any luck (tipps from above) - however I had the feeling it was a bit better with channel 6.

But now comes the interesting clue on the bug:
I have no issue when I open the octopi/octoprint site (on the pi) from my windows 10 or ubuntu 16 machine (using chrome, cable connection to the router). My guess is now it is a android, samsung or wifi to wifi related bug. And I think I have read something about android/rpi issues a while back.

Hope this helps. If you need a tester for some version I would give it a try.

DEvil0000 commented Jun 4, 2018

I have the same issue with octoPi 0.14 (every package updated, rpi firmware at latest, every octoprint plugin updated).

brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110

with this setup its 100% reproducable. Accassing the octoprint website on the pi (first time access after boot) from my samsung s4 active (android 5.0.1, using chrome) or from my samsung tablet 10inch note thing with also android 5.x i guess and chrome kills the wifi when the page is half loaded.
No cable connected to my Pi3, wifi on channel 11 with wpa2.
I tried disabling wifi power thing and switching to wifi channel 6 without any luck (tipps from above) - however I had the feeling it was a bit better with channel 6.

But now comes the interesting clue on the bug:
I have no issue when I open the octopi/octoprint site (on the pi) from my windows 10 or ubuntu 16 machine (using chrome, cable connection to the router). My guess is now it is a android, samsung or wifi to wifi related bug. And I think I have read something about android/rpi issues a while back.

Hope this helps. If you need a tester for some version I would give it a try.

@splitice

This comment has been minimized.

Show comment
Hide comment
@splitice

splitice Jul 9, 2018

Just thought I would chime here and say we have also seen what looks to be like WiFi related blocking stalls around this driver which may be related on another SBC. It's not Raspberry PI specific.

splitice commented Jul 9, 2018

Just thought I would chime here and say we have also seen what looks to be like WiFi related blocking stalls around this driver which may be related on another SBC. It's not Raspberry PI specific.

@bugok

This comment has been minimized.

Show comment
Hide comment
@bugok

bugok Jul 17, 2018

This is happening to me too.

Setup

  • Pi 3B 1.2 (a02082)
  • Kernel:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.54-v7+ #1126 SMP Wed Jul 11 20:01:03 BST 2018 armv7l GNU/Linux

Running Raspbian version 9.4:

pi@raspberrypi:~ $ cat /etc/debian_version
9.4

Firmware version:

pi@raspberrypi:~ $ /opt/vc/bin/vcgencmd version
Jul  9 2018 19:35:54
Copyright (c) 2012 Broadcom
version daa7178a0900fd9a743c019f9dad7889d531e71d (clean) (release)

wlan0 Power management is turned off:

pi@raspberrypi:~ $ iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"VIRUS_2.4"
          Mode:Managed  Frequency:2.462 GHz  Access Point: D4:7B:B0:79:AF:A6
          Bit Rate=72.2 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=47/70  Signal level=-63 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:120  Invalid misc:0   Missed beacon:0

I'm using the built-in wifi. Nothing is connected to the ethernet port.

System has been upgraded using apt-get upgrade, apt-get dist-upgrade and rpi-update.

What I see

After the pi has been up for about an hour, it becomes unreachable from the network. I can't reach the Pi from my local network (ping and ssh don't work).

In dmesg, I see that I get:

brcmfmac: power management disabled
...
snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned

But no errors.

Something interesting

I noticed that when this happens, if I connect to the pi directly and ping my laptop - things get back to work. Also, ping times are a bit odd - seems like it takes a little time to get things to 'warm up':

pi@raspberrypi:~ $ ping 192.168.1.22
PING 192.168.1.22 (192.168.1.22) 56(84) bytes of data.
64 bytes from 192.168.1.22: icmp_seq=1 ttl=64 time=5024 ms
64 bytes from 192.168.1.22: icmp_seq=2 ttl=64 time=4010 ms
64 bytes from 192.168.1.22: icmp_seq=3 ttl=64 time=2971 ms
64 bytes from 192.168.1.22: icmp_seq=4 ttl=64 time=1932 ms
64 bytes from 192.168.1.22: icmp_seq=5 ttl=64 time=892 ms
64 bytes from 192.168.1.22: icmp_seq=6 ttl=64 time=5.63 ms
64 bytes from 192.168.1.22: icmp_seq=7 ttl=64 time=12.4 ms
64 bytes from 192.168.1.22: icmp_seq=8 ttl=64 time=5.59 ms
64 bytes from 192.168.1.22: icmp_seq=9 ttl=64 time=55.5 ms

If anyone needs any more information, I'd be happy to supply it.

bugok commented Jul 17, 2018

This is happening to me too.

Setup

  • Pi 3B 1.2 (a02082)
  • Kernel:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.54-v7+ #1126 SMP Wed Jul 11 20:01:03 BST 2018 armv7l GNU/Linux

Running Raspbian version 9.4:

pi@raspberrypi:~ $ cat /etc/debian_version
9.4

Firmware version:

pi@raspberrypi:~ $ /opt/vc/bin/vcgencmd version
Jul  9 2018 19:35:54
Copyright (c) 2012 Broadcom
version daa7178a0900fd9a743c019f9dad7889d531e71d (clean) (release)

wlan0 Power management is turned off:

pi@raspberrypi:~ $ iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"VIRUS_2.4"
          Mode:Managed  Frequency:2.462 GHz  Access Point: D4:7B:B0:79:AF:A6
          Bit Rate=72.2 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=47/70  Signal level=-63 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:120  Invalid misc:0   Missed beacon:0

I'm using the built-in wifi. Nothing is connected to the ethernet port.

System has been upgraded using apt-get upgrade, apt-get dist-upgrade and rpi-update.

What I see

After the pi has been up for about an hour, it becomes unreachable from the network. I can't reach the Pi from my local network (ping and ssh don't work).

In dmesg, I see that I get:

brcmfmac: power management disabled
...
snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned

But no errors.

Something interesting

I noticed that when this happens, if I connect to the pi directly and ping my laptop - things get back to work. Also, ping times are a bit odd - seems like it takes a little time to get things to 'warm up':

pi@raspberrypi:~ $ ping 192.168.1.22
PING 192.168.1.22 (192.168.1.22) 56(84) bytes of data.
64 bytes from 192.168.1.22: icmp_seq=1 ttl=64 time=5024 ms
64 bytes from 192.168.1.22: icmp_seq=2 ttl=64 time=4010 ms
64 bytes from 192.168.1.22: icmp_seq=3 ttl=64 time=2971 ms
64 bytes from 192.168.1.22: icmp_seq=4 ttl=64 time=1932 ms
64 bytes from 192.168.1.22: icmp_seq=5 ttl=64 time=892 ms
64 bytes from 192.168.1.22: icmp_seq=6 ttl=64 time=5.63 ms
64 bytes from 192.168.1.22: icmp_seq=7 ttl=64 time=12.4 ms
64 bytes from 192.168.1.22: icmp_seq=8 ttl=64 time=5.59 ms
64 bytes from 192.168.1.22: icmp_seq=9 ttl=64 time=55.5 ms

If anyone needs any more information, I'd be happy to supply it.

@quozl

This comment has been minimized.

Show comment
Hide comment
@quozl

quozl Jul 17, 2018

Contributor

@bugok, does setting the network interface to promiscuous alleviate the problem for you? (ifconfig wlan0 promisc).

Contributor

quozl commented Jul 17, 2018

@bugok, does setting the network interface to promiscuous alleviate the problem for you? (ifconfig wlan0 promisc).

@bugok

This comment has been minimized.

Show comment
Hide comment
@bugok

bugok Jul 17, 2018

@quozl: It didn't help. After a while, ping started to fail:

$ ping 192.168.1.80
PING 192.168.1.80 (192.168.1.80): 56 data bytes
ping: sendto: No route to host
ping: sendto: Host is down
Request timeout for icmp_seq 0
...

bugok commented Jul 17, 2018

@quozl: It didn't help. After a while, ping started to fail:

$ ping 192.168.1.80
PING 192.168.1.80 (192.168.1.80): 56 data bytes
ping: sendto: No route to host
ping: sendto: Host is down
Request timeout for icmp_seq 0
...
@bugok

This comment has been minimized.

Show comment
Hide comment
@bugok

bugok Jul 19, 2018

Reporting back: My issue seems to be resolved, and seems to be unrelated to the problem in this thread.

Details here, but the gist is that I set a static IP on the Pi itself (in /etc/dhcpcd.conf). After defining the static IP in the router, removing the static IP config from /etc/dhcpcd.conf and rebooting - things seem to work.

bugok commented Jul 19, 2018

Reporting back: My issue seems to be resolved, and seems to be unrelated to the problem in this thread.

Details here, but the gist is that I set a static IP on the Pi itself (in /etc/dhcpcd.conf). After defining the static IP in the router, removing the static IP config from /etc/dhcpcd.conf and rebooting - things seem to work.

sasikrishna2014 pushed a commit to sasikrishna2014/ubuntu-bionic that referenced this issue Aug 7, 2018

Sets the BCDC priority to constant 0
This is to workaround for a possible issue in the
wireless chip firmware where some packets with
higher priorities seem to go missing.

See raspberrypi/linux#1342 for
details.
@randyoo

This comment has been minimized.

Show comment
Hide comment
@randyoo

randyoo Aug 25, 2018

A quick update: this issue ("Unknown mailbox data content" error accompanied by complete wireless lockup) persists, on the latest firmware with all updates installed (dist-upgrade).

Changing a single line in the hostapd.conf file (as per my previous comment) still eliminates the issue for me.

randyoo commented Aug 25, 2018

A quick update: this issue ("Unknown mailbox data content" error accompanied by complete wireless lockup) persists, on the latest firmware with all updates installed (dist-upgrade).

Changing a single line in the hostapd.conf file (as per my previous comment) still eliminates the issue for me.

@akarapatis

This comment has been minimized.

Show comment
Hide comment
@akarapatis

akarapatis Aug 28, 2018

Using Rpi3B with kernel 4.14.52-v7 (raspberrypi-kernel 1.20180703-1) and (firmware-brcm80211 1:20161130-3+rpt4)
I am also still facing the problem where wlan freezes (90 devices out of which 2 per day have the issue). In some cases the adapter is missing and in other it is not responding. I am not using the Pi in AP mode, just
I tried to rebind it as in RPi-3B+ but with no success.

I currently created a solution when no-network-connection is detected, the pi reboots. However, this is no proper solution and at least I am trying to reload the driver

akarapatis commented Aug 28, 2018

Using Rpi3B with kernel 4.14.52-v7 (raspberrypi-kernel 1.20180703-1) and (firmware-brcm80211 1:20161130-3+rpt4)
I am also still facing the problem where wlan freezes (90 devices out of which 2 per day have the issue). In some cases the adapter is missing and in other it is not responding. I am not using the Pi in AP mode, just
I tried to rebind it as in RPi-3B+ but with no success.

I currently created a solution when no-network-connection is detected, the pi reboots. However, this is no proper solution and at least I am trying to reload the driver

@pinoyyid

This comment has been minimized.

Show comment
Hide comment
@pinoyyid

pinoyyid Sep 8, 2018

I was consistently seeing this same problem on a previously working Pi 3. I realised that the only change I had made was to plug in an LCD touch screen, drawing power from the Pi. When I unplugged the touch screen, WiFi worked correctly. So it certainly seems to be power related. This was using the official Raspberry AC adaptor.

pinoyyid commented Sep 8, 2018

I was consistently seeing this same problem on a previously working Pi 3. I realised that the only change I had made was to plug in an LCD touch screen, drawing power from the Pi. When I unplugged the touch screen, WiFi worked correctly. So it certainly seems to be power related. This was using the official Raspberry AC adaptor.

@JamesH65

This comment has been minimized.

Show comment
Hide comment
@JamesH65

JamesH65 Sep 9, 2018

Contributor

That's a very interesting data point. Was it one of our LCD's?

Contributor

JamesH65 commented Sep 9, 2018

That's a very interesting data point. Was it one of our LCD's?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment