After 24 days the AX3600 rebooted with the auto reboot script after firmware error.
I assume thatās due to wifi crash right? Thatās the only reboot script Iāve seen floating around for this target.
My current uptime stands at 18 days, and memory is stable at about 100MB on the AX3600 router. Amazingly more stable than my three mediatek/mt7622 dumb AP devices (AX6S) which at exactly the same uptime are all standing with roughly 15MB free RAM. MTK tends to be very stable so this is quite interesting to be honest.
@robimarko I know everyone has an opinion on everything, but Iāll add mine 
I would recommend baking IRQ assignment values into the codebase to help the targetās stability and performance for those not involved enough in the community to know about this.
PS. This uptime could have been longer, but it was my last snapshot update. I couldnāt make it more than a day previously (after the 6.1 update which resulted in the IRQs changing, making my old hardcoded values useless).
1 Like
Great, can you email or PM me the script used?
Or you can make the PR to include the script by default
1 Like
For sure thank you!
I pasted the script into the GitHub ticket for the memory issue here: https://github.com/openwrt/openwrt/issues/13562#issuecomment-1817573570
The only thing I can think of missing given that my devices donāt have USB, is adding the USB IRQ names to get them off core 1. I have read that they must all be moved to the same core or the target will crash.
1 Like
Should we use chmod +x instead of chmod 777.
I've actually read that chmod XXX is 2-3 times more commonly used (although I personally tend to use +x etc more commonly day-to-day)
That's where Robi's knowlege of openwrt source preference comes into play.
But skip 777 please
You want chmod +x definitively just to allow executing, nothing else.
chmod 777 is a big NO NO
@Edrikk Can you also share the auto-restart script? How responsive is it?
I actually donāt use it, so donāt know the answer.
But hereās one from @uweklatt
EDIT: And we have completed the loop as that post points to the IRQ script as well
1 Like
The ath11k firmware is still buggy.
The crash happens, when a 2.4GHz client is leaving or reconnecting the network.
I use different SSIDs for 2.4GHz and 5GHz and the irq-balance script.
Version: OpenWrt SNAPSHOT r24685-4a2ff73177 / LuCI Master git-23.292.78363-ee6a4da
My newest crashlog:
Fri Dec 29 11:44:21 2023 daemon.info hostapd: phy2-ap1: STA 38:80:df:xx:xx:xx IEEE 802.11: authenticated
Fri Dec 29 11:44:21 2023 daemon.info hostapd: phy2-ap1: STA 38:80:df:xx:xx:xx IEEE 802.11: associated (aid 4)
Fri Dec 29 11:44:21 2023 daemon.notice hostapd: phy2-ap1: AP-STA-CONNECTED 38:80:df:xx:xx:xx auth_alg=open
Fri Dec 29 11:44:21 2023 daemon.info hostapd: phy2-ap1: STA 38:80:df:xx:xx:xx RADIUS: starting accounting session 1BBF26C48CCFCC2B
Fri Dec 29 11:44:21 2023 daemon.info hostapd: phy2-ap1: STA 38:80:df:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Fri Dec 29 11:44:21 2023 daemon.notice hostapd: phy2-ap1: EAPOL-4WAY-HS-COMPLETED 38:80:df:xx:xx:xx
Fri Dec 29 11:46:11 2023 daemon.notice hostapd: phy2-ap1: AP-STA-DISCONNECTED 38:80:df:xx:xx:xx
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523]
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] wal_peer_control.c:2904 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] Thread ID : 0x00000060 Thread name : WLAN RT1 Process ID : 0
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] Register:
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] SP : 0x4bfd5a48
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] FP : 0x4bfd5a50
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] PC : 0x4b1080c4
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] SSR : 0x00000008
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] BADVA : 0x00020000
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] LR : 0x4b107860
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523]
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] Stack Dump
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] from : 0x4bfd5a48
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523] to : 0x4bfd62a8
Fri Dec 29 11:46:11 2023 kern.err kernel: [471917.969523]
Fri Dec 29 11:46:11 2023 kern.err kernel: [471918.020252] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Fri Dec 29 11:46:11 2023 kern.err kernel: [471918.042496] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Fri Dec 29 11:46:11 2023 kern.err kernel: [471918.050553] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Fri Dec 29 11:46:11 2023 kern.info kernel: [471918.083520] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.106087] ath11k c000000.wifi: failed to transmit frame -108
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.367034] ath11k c000000.wifi: failed to find peer 38:80:df:xx:xx:xx on vdev 1 after creation
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.367081] ath11k c000000.wifi: failed to find peer vdev_id 1 addr 38:80:df:xx:xx:xx in delete
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.374892] ath11k c000000.wifi: failed peer 38:80:df:xx:xx:xx delete vdev_id 1 fallback ret -22
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.383687] ath11k c000000.wifi: Failed to add peer: 38:80:df:xx:xx:xx for VDEV: 1
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.392440] ath11k c000000.wifi: Failed to add station: 38:80:df:xx:xx:xx for VDEV: 1
Fri Dec 29 11:46:11 2023 daemon.notice hostapd: phy2-ap0: STA 38:80:df:xx:xx:xx IEEE 802.11: Could not add STA to kernel driver
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.437447] ath11k c000000.wifi: failed to update rx tid queue, tid 0 (-108)
Fri Dec 29 11:46:11 2023 kern.warn kernel: [471918.437478] ath11k c000000.wifi: failed to update reo for rx tid 0: -108
Fri Dec 29 11:46:11 2023 kern.info kernel: [471918.443558] phy2-ap1: HW problem - can not stop rx aggregation for 38:80:df:xx:xx:xx tid 0
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.497056] ath11k c000000.wifi: failed to send WMI_PEER_DELETE cmd
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.497087] ath11k c000000.wifi: failed to delete peer vdev_id 2 addr 38:80:df:xx:xx:xx ret -108
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.502533]
------------[ cut here ]------------
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.511236] WARNING: CPU: 2 PID: 1654 at sta_set_sinfo+0xcb4/0xd30 [mac80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.515928] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_inet ath11k_ahb ath11k ath10k_pci ath10k_core ath wireguard pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211 libchacha20poly1305 chacha_neon cfg80211 slhc qrtr_smd qrtr qmi_helpers poly1305_neon nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcurve25519_generic libcrc32c libchacha compat ip6_udp_tunnel udp_tunnel sha512_generic seqiv jitterentropy_rng drbg michael_mic kpp hmac cmac leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom qca_nss_dp qca_ssdk gpio_button_hotplug ext4 mbcache jbd2 aquantia hwmon crc_ccitt crc32c_generic
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.578847] CPU: 2 PID: 1654 Comm: hostapd Not tainted 6.1.69 #0
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.601082] Hardware name: Xiaomi AX3600 (DT)
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.607069] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.611414] pc : sta_set_sinfo+0xcb4/0xd30 [mac80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.618615] lr : sta_set_sinfo+0xcb0/0xd30 [mac80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.623562] sp : ffffffc00d0a3870
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.628681] x29: ffffffc00d0a3870 x28: ffffff800447e000 x27: ffffffc00d0a3dc8
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.632073] x26: ffffff8002077080 x25: ffffffc008cca400 x24: ffffff8010610940
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.639278] x23: ffffff8014b25ab8 x22: ffffff8010610940 x21: ffffff80065108a0
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.646483] x20: 0000000000000001 x19: ffffff8014b25000 x18: 0000000000000187
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.653687] x17: 3a30383a38332072 x16: 6464612032206469 x15: ffffffc008bc7328
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.660892] x14: 0000000000000495 x13: 0000000000000187 x12: 00000000ffffffea
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.668098] x11: ffffffc000e22390 x10: ffffffc00d0a3750 x9 : ffffffc00d0a3770
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.675302] x8 : 0000000000000024 x7 : ffffff8013da2000 x6 : 0000000000008e20
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.682508] x5 : ffffffc0173f2000 x4 : 0000000000000000 x3 : ffffff800447e000
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.689712] x2 : 0000000000000000 x1 : ffffff800447e000 x0 : 00000000ffffff94
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.696917] Call trace:
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.704113] sta_set_sinfo+0xcb4/0xd30 [mac80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.706809] sta_info_destroy_addr_bss+0x54/0x80 [mac80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.711411] ieee80211_color_change_finish+0x1c68/0x1f80 [mac80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.717228] cfg80211_check_station_change+0x1268/0x3530 [cfg80211]
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.723566] genl_family_rcv_msg_doit+0xb8/0x11c
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.729898] genl_rcv_msg+0x108/0x230
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.734498] netlink_rcv_skb+0x5c/0x12c
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.738144] genl_rcv+0x38/0x50
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.742221] netlink_unicast+0x1e8/0x2d4
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.745434] netlink_sendmsg+0x1a0/0x3d0
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.749341] ____sys_sendmsg+0x1c8/0x270
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.753334] ___sys_sendmsg+0x7c/0xc0
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.757326] __sys_sendmsg+0x48/0xb0
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.760972] __arm64_sys_sendmsg+0x24/0x30
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.764706] invoke_syscall.constprop.0+0x5c/0x104
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.768699] do_el0_svc+0x58/0x17c
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.773558] el0_svc+0x18/0x54
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.777036] el0t_64_sync_handler+0xf4/0x120
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.780157] el0t_64_sync+0x174/0x178
Fri Dec 29 11:46:12 2023 kern.warn kernel: [471918.784671]
---[ end trace 0000000000000000 ]---
2 Likes
Just as un update: on the OpenWrt 23.05.2, r23630-842932a63d release, after deploying the irq balance script and removing the same SSID from both radios, I don't have hard crashes, but the wi-fi is still unstable - I'm getting transient failures in packet transmission, when they happen I get this "failed to flush" message as below
# dmesg | grep ath11k
[ 10.548357] ath11k c000000.wifi: ipq8074 hw2.0
[ 10.548396] ath11k c000000.wifi: FW memory mode: 1
[ 11.865449] ath11k c000000.wifi: qmi ignore invalid mem req type 3
[ 11.872899] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[ 11.872954] ath11k c000000.wifi: fw_version 0x290c84a5 fw_build_timestamp 2023-03-25 07:34 fw_build_id WLAN.HK.2.9.0.1-01385-QCAHKSWPL_SILICONZ-1
[ 12.083951] ath11k c000000.wifi: htt event 48 not handled
[41648.186820] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
I have 'software/hardware flow offloading' turned off and SQM on.
Just FYI that the script is now implemented in Master https://github.com/openwrt/openwrt/commit/ad25cfb6b8a282e47344fba59f42af61e115a8df
So no need to manually have it created/run any longer.
2 Likes
Good to know!
I'm currently looking for new hardware because the Xiaomi AX3600 is so annoying! I have extremely unstable wifi and it is not getting any better. I am using 2 of the Xiaomis as dump APs and have 6 SSIDs. The IOT vlan contains about 60 devices (40/20), the media vlan (incl. Alexas) about 10, the printer vlan 2, the children vlans about 6, the parents vlan about 6 and the admin vlan only 2 devices.
Since I split it into 5G only and 2G only networks, it feels even worse as I now have constant dropouts on the 5G networks. Maybe it's always been like this and I didn't realise it because the fallback to the 2G network was there.
Yesterday I completely reinstalled both Xiaomis and changed some wifi settings (Station inactivity limit and Disassociate On Low Acknowledgement) but nothing helps. This morning the logfile is again full of errors and the wifi is unstable again.
The sad/weird thing is: I am very sure that it worked much better in the beginning with robimarko's images (before it was included as a snapshot). Back then, I only had to restart the two APs about once a week, had 2G and 5G networks and almost no dropouts. I can only dream of that today!
Mon Feb 5 07:25:14 2024 kern.warn kernel: [39627.472773] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 43
Mon Feb 5 07:25:19 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:25:30 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:25:35 2024 kern.warn kernel: [39647.712775] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 53
Mon Feb 5 07:25:40 2024 kern.warn kernel: [39652.832783] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 47
Mon Feb 5 07:25:45 2024 kern.warn kernel: [39657.872772] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 54
Mon Feb 5 07:26:10 2024 kern.warn kernel: [39683.312798] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
Mon Feb 5 07:26:15 2024 daemon.notice hostapd: phy2-ap0: AP-STA-DISCONNECTED 7c:49:eb:b3:a7:5d
Mon Feb 5 07:26:15 2024 daemon.info hostapd: phy2-ap0: STA 7c:49:eb:b3:a7:5d IEEE 802.11: disassociated due to inactivity
Mon Feb 5 07:26:20 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:26:25 2024 daemon.info hostapd: phy2-ap0: STA 7c:49:eb:b3:a7:5d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Feb 5 07:26:30 2024 kern.warn kernel: [39703.472864] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 36
Mon Feb 5 07:26:41 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:26:51 2024 kern.warn kernel: [39723.712833] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 65
Mon Feb 5 07:26:56 2024 daemon.err collectd[2129]: plugin_read_thread: read-function of the `iwinfo' plugin took 32.316 seconds, which is above its read interval (30.000 seconds). You might want to adjust the `Interval' or `ReadThreads' settings.
Mon Feb 5 07:26:56 2024 kern.warn kernel: [39728.832839] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 69
Mon Feb 5 07:27:01 2024 kern.warn kernel: [39733.952848] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 51
Mon Feb 5 07:27:06 2024 kern.warn kernel: [39739.072843] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 57
Mon Feb 5 07:27:06 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:27:11 2024 kern.warn kernel: [39744.192848] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 55
Mon Feb 5 07:27:21 2024 kern.warn kernel: [39754.432859] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 57
Mon Feb 5 07:27:26 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
[...]
Mon Feb 5 07:34:59 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 5 07:34:59 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 5 07:34:59 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:34:59 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:35:00 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:35:00 2024 daemon.notice hostapd: phy2-ap2: STA 04:d6:aa:6a:d4:73 IEEE 802.11: did not acknowledge authentication response
[...]
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: did not acknowledge authentication response
Mon Feb 5 07:58:24 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:58:24 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:58:24 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:58:24 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:58:24 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:58:24 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:7f:40:15 IEEE 802.11: authenticated
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:24 2024 daemon.notice hostapd: handle_assoc_cb: STA 04:cf:8c:78:bc:0b not found
Mon Feb 5 07:58:32 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:78:bc:0b IEEE 802.11: authenticated
Mon Feb 5 07:58:32 2024 daemon.info hostapd: phy2-ap0: STA 04:cf:8c:78:bc:0b IEEE 802.11: associated (aid 16)
And the dmesg output:
# dmesg | grep ath11k
[ 10.025453] ath11k c000000.wifi: ipq8074 hw2.0
[ 10.025492] ath11k c000000.wifi: FW memory mode: 1
[ 11.331619] ath11k c000000.wifi: qmi ignore invalid mem req type 3
[ 11.339036] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[ 11.339096] ath11k c000000.wifi: fw_version 0x290104a5 fw_build_timestamp 2023-08-02 20:32 fw_build_id WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1
[ 11.552074] ath11k c000000.wifi: htt event 48 not handled
[ 6288.397318] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[ 6530.717325] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[ 6535.757345] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 25
[ 6570.717320] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[ 6639.357316] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 48
[ 6654.477328] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 54
[ 6669.677337] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 64
[ 6709.197327] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 11
[ 6714.317314] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 14
[ 6753.437324] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 52
[ 6763.597307] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 11
[ 6788.957295] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[ 6799.117299] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 37
[ 6824.317288] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 6
[12309.922885] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 4
[13396.485097] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[19636.893608] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 2
[20837.694817] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3
[29645.704125] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3
[33953.068444] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[39081.152349] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 34
[39086.272324] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 39
[39091.392328] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 41
[39096.512339] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 24
[39101.632352] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 16
[39106.752339] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 30
[39111.872344] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 40
[39116.992347] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 52
[39122.112357] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 46
[39127.232354] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 49
[39132.352357] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 48
[39137.472365] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 35
[39142.592366] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 36
[39162.832390] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 52
[39172.832390] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 44
[39187.952417] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 38
[39193.072408] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 36
[39198.192412] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 43
[39203.312435] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 37
[39208.432418] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 22
[39213.552422] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 35
I switched to two "cudy WR3000 v1" and it's incredible! Now I have stable WIFI with all VLANS with 5G/2.4G networks for almost 4 days. So far, there hasn't been a single dropout and it's running better than ever with the Xiaomis. It's a real relief for the whole family here, as we now have stable WIFI for the first time in months. I paid about 90ā¬ (45ā¬ each) and I wish I had changed the hardware much sooner.
1 Like
Is there an option to use this newer Qualcom fimware?
Replacing the existing board-2.bin does not work. The newer file is much bigger than the "old" one.
1 Like
Sad to hear that the AX3600 is so unstable.
Bought mine in the very beginning but didn't manage to replace my wifi5/AC-Accesspoints yet.
Looks like that saved me a lot of trouble.
While I still hope that we can get the AX3600 stabilized, maybe with the new Firmware that was pointed out in the previous post by @uweklatt, personally I'm not sure whether to use them at all, with Stock FW, OpenWrt or simply buy a MT-based AX-device and flash OpenWrt.
This is only bdf, not firmware.
1 Like
I do not experience instability here, using 24700 snapshot + irqBalance script + daily reboot and vlan/5 ssid's each on two xiaomi ax3600.