Wifi down - Solution is to reboot

Hi friends, I have a problem with a Nexx WT3020 (8M) router.
I installed OpenWrt 18.06.4.
Wifi is continuously down, at least once a day I have to restart the router to make it work.
Here is the log of what happens:

Mon Aug  5 11:52:27 2019 user.notice mac80211: Failed command: iw phy phy0 set antenna all all
Mon Aug  5 11:52:27 2019 daemon.notice netifd: radio0 (1096): command failed: Not supported (-122)
Mon Aug  5 11:52:27 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Mon Aug  5 11:52:28 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Mon Aug  5 11:52:29 2019 kern.info kernel: [   26.248870] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mon Aug  5 11:52:29 2019 kern.info kernel: [   26.266530] br-lan: port 3(wlan0) entered blocking state
Mon Aug  5 11:52:29 2019 kern.info kernel: [   26.277215] br-lan: port 3(wlan0) entered disabled state
Mon Aug  5 11:52:29 2019 kern.info kernel: [   26.288158] device wlan0 entered promiscuous mode
Mon Aug  5 11:52:29 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Aug  5 11:52:29 2019 daemon.err hostapd: Using interface wlan0 with hwaddr 20:28:18:a1:fe:26 and ssid "Marianto"
Mon Aug  5 11:52:30 2019 kern.info kernel: [   26.822645] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mon Aug  5 11:52:30 2019 kern.info kernel: [   26.835540] br-lan: port 3(wlan0) entered blocking state
Mon Aug  5 11:52:30 2019 kern.info kernel: [   26.846165] br-lan: port 3(wlan0) entered forwarding state
Mon Aug  5 11:52:30 2019 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ENABLED
Mon Aug  5 11:52:30 2019 daemon.notice hostapd: wlan0: AP-ENABLED
Mon Aug  5 11:52:30 2019 daemon.notice netifd: Network device 'wlan0' link is up
Mon Aug  5 11:52:31 2019 daemon.info hostapd: wlan0: STA 5c:cf:7f:53:dc:95 IEEE 802.11: authenticated
Mon Aug  5 11:52:31 2019 daemon.info hostapd: wlan0: STA 5c:cf:7f:53:dc:95 IEEE 802.11: associated (aid 1)
Mon Aug  5 11:52:31 2019 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 5c:cf:7f:53:dc:95
Mon Aug  5 11:52:31 2019 daemon.info hostapd: wlan0: STA 5c:cf:7f:53:dc:95 WPA: pairwise key handshake completed (WPA)
Mon Aug  5 11:52:32 2019 daemon.info hostapd: wlan0: STA 5c:cf:7f:53:dc:95 WPA: group key handshake completed (WPA)
Mon Aug  5 11:53:35 2019 kern.notice kernel: [   49.237498] random: crng init done
Mon Aug  5 12:34:55 2019 daemon.info hostapd: wlan0: STA a0:20:a6:03:dd:c7 IEEE 802.11: authenticated
Mon Aug  5 12:34:55 2019 daemon.info hostapd: wlan0: STA a0:20:a6:03:dd:c7 IEEE 802.11: associated (aid 2)
Mon Aug  5 12:34:55 2019 daemon.notice hostapd: wlan0: AP-STA-CONNECTED a0:20:a6:03:dd:c7
Mon Aug  5 12:34:55 2019 daemon.info hostapd: wlan0: STA a0:20:a6:03:dd:c7 WPA: pairwise key handshake completed (WPA)
Mon Aug  5 12:34:56 2019 daemon.info hostapd: wlan0: STA a0:20:a6:03:dd:c7 WPA: group key handshake completed (WPA)
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.130661] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.149086] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.167498] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.185900] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.204301] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.222711] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.241117] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.259516] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.277916] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.296315] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.314711] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.333106] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.351501] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.369896] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.388292] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.406685] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.425080] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.443476] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.461870] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 13:20:26 2019 kern.err kernel: [ 1805.480265] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Mon Aug  5 15:12:00 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: authenticated
Mon Aug  5 15:12:00 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: associated (aid 3)
Mon Aug  5 15:12:00 2019 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:95:c7:f5:62:a4
Mon Aug  5 15:12:00 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 WPA: pairwise key handshake completed (WPA)
Mon Aug  5 15:12:01 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 WPA: group key handshake completed (WPA)
Mon Aug  5 15:13:32 2019 daemon.notice hostapd: wlan0: STA a4:50:46:27:ee:fb IEEE 802.11: did not acknowledge authentication response
Mon Aug  5 15:18:06 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:95:c7:f5:62:a4
Mon Aug  5 15:18:06 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: disassociated due to inactivity
Mon Aug  5 15:18:07 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Aug  5 15:18:35 2019 daemon.info hostapd: wlan0: STA a4:50:46:27:ee:fb IEEE 802.11: disassociated due to inactivity
Mon Aug  5 15:18:36 2019 daemon.info hostapd: wlan0: STA a4:50:46:27:ee:fb IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Aug  5 15:22:10 2019 kern.info kernel: [ 4269.255954] mtk_soc_eth 10100000.ethernet eth0: port 4 link up (100Mbps/Full duplex)
Mon Aug  5 15:23:44 2019 kern.info kernel: [ 4301.351871] mtk_soc_eth 10100000.ethernet eth0: port 4 link down
Mon Aug  5 18:20:01 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: authenticated
Mon Aug  5 18:20:01 2019 daemon.notice hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: did not acknowledge authentication response
Mon Aug  5 18:20:01 2019 daemon.notice hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: did not acknowledge authentication response
Mon Aug  5 18:20:02 2019 daemon.notice hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: did not acknowledge authentication response
Mon Aug  5 18:20:02 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 IEEE 802.11: associated (aid 3)
Mon Aug  5 18:20:02 2019 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:95:c7:f5:62:a4
Mon Aug  5 18:20:02 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 WPA: pairwise key handshake completed (WPA)
Mon Aug  5 18:20:02 2019 daemon.info hostapd: wlan0: STA f8:95:c7:f5:62:a4 WPA: group key handshake completed (WPA)
Mon Aug  5 18:57:35 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:95:c7:f5:62:a4

Thanks

I have not looked into it in any depth, but this appears to be a common problem

https://forum.openwrt.org/search?q=rt2x00queue_write_tx_frame

One (older) post from a member whose insight I find valuable is

1 Like

There has been pretty targeted work on this recently (kernel upstream, and from there to master --> snapshots), hopefully it is fixed (or at least better) there.

1 Like

Slightly surprised to hear that, and man was that bug ever annoying.

I no longer have it for OP but I resorted to a small shell script started in rc.local that watched the output of "logread -f" and when there was a line that matched "Dropping frame due to full tx queue 2" it would reboot the router automatically, which worked fine in the interim until I replaced that router. I didn't use the "-e" option of logread as I was relying on the return value of grep to trigger the reboot.

EDIT: Well, the patch information was...interesting.

For unknown reasons printk() on some context can cause CPU hung on embedded MT7620 AP/router MIPS platforms. What can result on wifi disconnects.

This patch move queue full messages to debug level what is consistent with other mac80211 drivers which drop packet silently if tx queue is full. This make MT7620 OpenWRT routers more stable, what was reported by various users.

I fiddled around with Padavan back then and it was stable. Since this brought up some memories I went digging, and it looks like the 3.4 kernel was using ERROR instead of the rt2x00_err function. I wonder when that was changed.

It's fixed in snapshot and 19.07

1 Like

Are you sure about that? Seems to still exist in 19.07, at least for me.

You can use a workaround like this one:
After every 5-7 days uptime openwrt 19.07.4 dissociates clients - #2 by vgaetera

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.