Description of problem: I am running wifi access point on Raspberry pi 3 (hostapd) using the internal wifi. This is on Fedora 26 with: Linux server 4.12.14-300.fc26.armv7hl #1 SMP Wed Sep 20 18:05:42 UTC 2017 armv7l armv7l armv7l GNU/Linux After a couple of hours of service, the wifi dies and I can see the following dmesg: [ 708.227802] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012 [ 768.291280] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 770.851290] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 770.851514] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 774.819307] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 777.379307] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 777.379532] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 786.595388] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 789.155381] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 789.155605] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 954.277113] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 956.837151] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 956.837374] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 959.397171] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 961.957221] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 961.964953] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 976.101406] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 978.661457] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 978.669110] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 1080.934043] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 1083.494063] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 1083.501735] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 1086.054092] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 1088.614096] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 1088.621767] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 1093.670124] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 1096.230194] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [ 1096.237847] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [ 1238.312294] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1239.272283] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets [ 1241.832258] brcmfmac: send_key_to_dongle: wsec_key error (-110) [ 1244.392241] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 [ 1246.952222] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1249.512225] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 [ 1252.072210] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1254.632171] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 [ 1257.192177] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1259.752122] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 [ 1262.312100] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1264.872090] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 [ 1265.832090] brcmfmac: brcmf_netdev_wait_pend8021x: Timed out waiting for no pending 802.1x packets [ 1268.392079] brcmfmac: send_key_to_dongle: wsec_key error (-110) [ 1270.952035] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1273.512032] brcmfmac: brcmf_cfg80211_change_station: Setting SCB (de-)authorize failed, -110 [ 1276.072004] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1278.632008] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1281.191959] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1283.751963] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1286.311926] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1288.871947] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1291.431936] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1293.991961] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1296.551965] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1299.111925] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1301.671930] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 [ 1304.231971] brcmfmac: brcmf_cfg80211_del_station: SCB_DEAUTHENTICATE_FOR_REASON failed -110 Trying rmmod and modprobe does gives: [11347.369913] usbcore: deregistering interface driver brcmfmac [11351.261249] usbcore: registered new interface driver brcmfmac [11353.832662] net_ratelimit: 14 callbacks suppressed [11353.836102] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [11353.839490] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -110 [11353.846368] brcmfmac: brcmf_bus_started: failed: -110 [11353.849848] brcmfmac: brcmf_sdio_firmware_callback: dongle is not responding I gather from googling around that this may be related to power management (iwconfig wlan0 power off) but I will check that. If that turns out to be the case, the default should be to disable it.
OK, this is a power saving mode issue. Adding the following: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="brcmfmac", KERNEL=="wlan0", RUN="/sbin/iwconfig wlan0 power off" to /etc/udev/rules.d/70-persistent-net.rules solves the problem (perhaps rename the file to something with brcmfmac in it). This should be made the default until power saving works properly in this driver. There is also another peculiar issue. I had wpa=3 /etc/hostapd/hostapd.conf in my access point (Fedora 26) and this seemed to allow WPA to some (Raspbian based RPI3) clients. This led to "brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: ..." appearing in their dmesg and the wireless would stop working on them (reboot needed; the fedora access point was not affected). Changing to wpa=2 in my access point made this problem go away. I did not see this in fedora clients but the problem might be there too.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.