ajayk111
Posts: 4
Joined: Tue Apr 13, 2021 10:58 pm

RasPi 4 WiFi Stops working after some time

Tue Apr 13, 2021 11:10 pm

I'm currently running the latest version of Raspbian. I'm using my Pi as a NAS, but every few hours the wifi goes down and I need to reboot in order to connect to the internet again. I've checked and wifi power management is turned off, so that shouldn't be affecting this.

kernel.log seems to have this around when the wifi last went down:

Code: Select all

Apr 13 07:10:28 raspberrypi kernel: [26059.747265] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26059.883974] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26059.884797] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26060.383744] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26060.383939] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:41 raspberrypi kernel: [26073.246942] mmc1: Timeout waiting for hardware interrupt.
Apr 13 07:10:41 raspberrypi kernel: [26073.247221] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Apr 13 07:10:41 raspberrypi kernel: [26073.247244] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:51 raspberrypi kernel: [26083.486951] mmc1: Timeout waiting for hardware interrupt.
Apr 13 07:10:51 raspberrypi kernel: [26083.487448] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Apr 13 07:10:51 raspberrypi kernel: [26083.487470] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:13:13 raspberrypi kernel: [26224.999285] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Apr 13 07:13:13 raspberrypi kernel: [26224.999293] brcmfmac: brcmf_sdio_rxfail: terminate frame
Apr 13 07:13:13 raspberrypi kernel: [26224.999402] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Apr 13 07:13:13 raspberrypi kernel: [26224.999409] brcmfmac: brcmf_sdio_rxfail: terminate frame
I also have this output in syslog:

Code: Select all

Apr 13 07:10:28 raspberrypi kernel: [26059.747265] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26059.883974] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26059.884797] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26060.383744] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:28 raspberrypi kernel: [26060.383939] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:41 raspberrypi kernel: [26073.246942] mmc1: Timeout waiting for hardware interrupt.
Apr 13 07:10:41 raspberrypi kernel: [26073.247221] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Apr 13 07:10:41 raspberrypi kernel: [26073.247244] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:10:51 raspberrypi kernel: [26083.486951] mmc1: Timeout waiting for hardware interrupt.
Apr 13 07:10:51 raspberrypi kernel: [26083.487448] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Apr 13 07:10:51 raspberrypi kernel: [26083.487470] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Apr 13 07:13:13 raspberrypi kernel: [26224.999285] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Apr 13 07:13:13 raspberrypi kernel: [26224.999293] brcmfmac: brcmf_sdio_rxfail: terminate frame
Apr 13 07:13:13 raspberrypi kernel: [26224.999402] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Apr 13 07:13:13 raspberrypi kernel: [26224.999409] brcmfmac: brcmf_sdio_rxfail: terminate frame
Apr 13 07:13:13 raspberrypi kernel: [26224.999515] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Apr 13 07:13:13 raspberrypi kernel: [26224.999522] brcmfmac: brcmf_sdio_rxfail: terminate frame

ajayk111
Posts: 4
Joined: Tue Apr 13, 2021 10:58 pm

Re: RasPi 4 WiFi Stops working after some time

Thu Apr 15, 2021 9:39 pm

Update: it seems like if I try to access the pi using mDNS (eg raspberrypi.lan) instead of its local IP address I can still access it. Running ip link shows the state as DORMANT for wlan0. if I try setting the state back to DEFAULT, it seems like I can ping external ip addresses (eg 8.8.8.8), however running something like ping google.com gives me

Code: Select all

ping: google.com: Temporary failure in name resolution
.

User avatar
kerry_s
Posts: 2046
Joined: Thu Jan 30, 2020 7:14 pm

Re: RasPi 4 WiFi Stops working after some time

Thu Apr 15, 2021 10:33 pm

sounds like a dns issue.
setup your own in the pi.

i've seen that kind of error when i reboot my pihole which provides my dns.

ajayk111
Posts: 4
Joined: Tue Apr 13, 2021 10:58 pm

Re: RasPi 4 WiFi Stops working after some time

Fri Apr 16, 2021 12:00 am

My pi just went down again and ssh using the local IP address or mDNS isn't working, so I think the name resolution issue could be a different issue. Also the issue usually happens around a few hours after boot. Journalctl seems to have a lot of instances of

Code: Select all

wpa_supplicant[503]: RRM: Ignoring radio measurement request: Not RRM network
but I'm not sure if this is related. After rebooting, checking the output of dig google.com and resolv.conf, both show that my DNS server is set correctly

User avatar
kerry_s
Posts: 2046
Joined: Thu Jan 30, 2020 7:14 pm

Re: RasPi 4 WiFi Stops working after some time

Fri Apr 16, 2021 12:28 am

how far from router, these pi"s are short range

ajayk111
Posts: 4
Joined: Tue Apr 13, 2021 10:58 pm

Re: RasPi 4 WiFi Stops working after some time

Fri Apr 16, 2021 3:07 am

The pi is on the 2nd floor, while the router is on the first, however, aside from that, they are relatively close. iwconfig wlan0 shows that the signal strength is -64dBm, which seems to be relatively strong.

Return to “Troubleshooting”