It seems ath11k still have problems as per log at the bottom.
Using 802.1x I have STA disconntection every a while. With standard WPA2 it seems the problem disappear.
AP Model is EdgeCore EAP102
Any suggestion?
Thanks in advance
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.148141] ath11k c000000.wifi: failed to transmit frame -12
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.153698] ath11k c000000.wifi: failed to transmit frame -12
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.159476] ath11k c000000.wifi: failed to transmit frame -12
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.165174] ath11k c000000.wifi: failed to transmit frame -12
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.170983] ath11k c000000.wifi: failed to transmit frame -12
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.176633] ath11k c000000.wifi: failed to transmit frame -12
Wed Mar 19 08:47:46 2025 kern.warn kernel: [ 2226.182374] ath11k c000000.wifi: failed to transmit frame -12
I am running a fresh build of main with 44 hours of uptime. I can’t remember ever seeing such messages on my GL-iNet GL-AX1800, running a vanilla OpenWrt based build for the past couple of months. Here is a section of my dmesg output that includes the first and last messages that mention ath11k:
[ 11.186653] ath11k c000000.wifi: ipq6018 hw1.0
[ 11.186689] ath11k c000000.wifi: FW memory mode: 1
[ 11.250139] remoteproc remoteproc0: powering up cd00000.remoteproc
[ 11.269709] remoteproc remoteproc0: Booting fw image IPQ6018/q6_fw.mdt, size 7340
[ 12.389575] remoteproc remoteproc0: remote processor cd00000.remoteproc is now up
[ 12.390944] ath11k c000000.wifi: qmi fail to get qcom,m3-dump-addr, ignore m3 dump mem req
[ 12.396632] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0xff soc_id 0xffffffff
[ 12.404238] ath11k c000000.wifi: fw_version 0x25008f8e fw_build_timestamp 2024-03-01 03:54 fw_build_id WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
[ 12.414106] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 16.388845] br-lan: port 1(lan1) entered blocking state
[ 16.388893] br-lan: port 1(lan1) entered disabled state
[ 16.392966] nss-dp 3a001200.dp2 lan1: entered allmulticast mode
[ 16.398329] nss-dp 3a001200.dp2 lan1: entered promiscuous mode
[ 16.412989] br-lan: port 2(lan2) entered blocking state
[ 16.413033] br-lan: port 2(lan2) entered disabled state
[ 16.417070] nss-dp 3a001400.dp3 lan2: entered allmulticast mode
[ 16.422673] nss-dp 3a001400.dp3 lan2: entered promiscuous mode
[ 16.434532] br-lan: port 3(lan3) entered blocking state
[ 16.434589] br-lan: port 3(lan3) entered disabled state
[ 16.439239] nss-dp 3a001600.dp4 lan3: entered allmulticast mode
[ 16.444677] nss-dp 3a001600.dp4 lan3: entered promiscuous mode
[ 16.455161] br-lan: port 4(lan4) entered blocking state
[ 16.456182] br-lan: port 4(lan4) entered disabled state
[ 16.461333] nss-dp 3a001800.dp5 lan4: entered allmulticast mode
[ 16.466843] nss-dp 3a001800.dp5 lan4: entered promiscuous mode
[ 17.163655] br-lan: port 5(phy1-ap0) entered blocking state
[ 17.163706] br-lan: port 5(phy1-ap0) entered disabled state
[ 17.168095] ath11k c000000.wifi phy1-ap0: entered allmulticast mode
[ 17.173879] ath11k c000000.wifi phy1-ap0: entered promiscuous mode
[ 17.180028] br-lan: port 5(phy1-ap0) entered blocking state
[ 17.186161] br-lan: port 5(phy1-ap0) entered forwarding state
[ 18.132790] br-lan: port 6(phy0-ap0) entered blocking state
[ 18.132832] br-lan: port 6(phy0-ap0) entered disabled state
[ 18.137210] ath11k c000000.wifi phy0-ap0: entered allmulticast mode
[ 18.143021] ath11k c000000.wifi phy0-ap0: entered promiscuous mode
To my understanding, the ath11k firmware was very recently updated in the main branch. Which firmware version are you using?
thank you for your answer, I'm running OpenWrt 24.10.0-rc2, r28161-ea17e958b9.
I'm going to update to last stable release, and then we see. However follow my dmesg.
[ 12.480712] ath11k c000000.wifi: ipq8074 hw2.0
[ 12.480748] ath11k c000000.wifi: FW memory mode: 0
[ 12.519281] remoteproc remoteproc0: powering up cd00000.q6v5_wcss
[ 12.519691] remoteproc remoteproc0: Booting fw image IPQ8074/q6_fw.mdt, size 668
[ 13.757213] remoteproc remoteproc0: remote processor cd00000.q6v5_wcss is now up
[ 13.801159] ath11k c000000.wifi: qmi ignore invalid mem req type 3
[ 13.808624] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[ 13.808661] ath11k c000000.wifi: fw_version 0x290b84a5 fw_build_timestamp 2024-09-23 11:32 fw_build_id WLAN.HK.2.9.0.1-02146-QCAHKSWPL_SILICONZ-1
[ 18.649764] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
[ 18.649809] remoteproc remoteproc0: powering up cd00000.q6v5_wcss
[ 18.655972] remoteproc remoteproc0: Booting fw image IPQ8074/q6_fw.mdt, size 668
[ 19.008824] remoteproc remoteproc0: remote processor cd00000.q6v5_wcss is now up
[ 19.011947] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 19.052772] ath11k c000000.wifi: qmi ignore invalid mem req type 3
[ 19.060219] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[ 19.060273] ath11k c000000.wifi: fw_version 0x290b84a5 fw_build_timestamp 2024-09-23 11:32 fw_build_id WLAN.HK.2.9.0.1-02146-QCAHKSWPL_SILICONZ-1
[ 19.361882] ath11k c000000.wifi: htt event 48 not handled
[ 21.731850] br-br173: port 1(wan.173) entered blocking state
[ 21.731896] br-br173: port 1(wan.173) entered disabled state
[ 21.736730] wan.173: entered allmulticast mode
[ 21.742234] nss-dp 3a001a00.dp6 wan: entered allmulticast mode
[ 21.746805] wan.173: entered promiscuous mode
[ 21.752300] nss-dp 3a001a00.dp6 wan: entered promiscuous mode
[ 21.838407] br-lan: port 1(lan) entered blocking state
[ 21.838456] br-lan: port 1(lan) entered disabled state
[ 21.842501] nss-dp 3a001800.dp5 lan: entered allmulticast mode
[ 21.848165] nss-dp 3a001800.dp5 lan: entered promiscuous mode
[ 23.636565] br-br173: port 2(wlan173_2) entered blocking state
[ 23.636621] br-br173: port 2(wlan173_2) entered disabled state
[ 23.641370] ath11k c000000.wifi wlan173_2: entered allmulticast mode
[ 23.647468] ath11k c000000.wifi wlan173_2: entered promiscuous mode
[ 23.657934] ath11k c000000.wifi wlan173_2: left allmulticast mode
[ 23.659635] ath11k c000000.wifi wlan173_2: left promiscuous mode
[ 23.666046] br-br173: port 2(wlan173_2) entered disabled state
[ 23.750520] br-br173: port 2(wlan173_2) entered blocking state
[ 23.750566] br-br173: port 2(wlan173_2) entered disabled state
[ 23.755420] ath11k c000000.wifi wlan173_2: entered allmulticast mode
[ 23.761354] ath11k c000000.wifi wlan173_2: entered promiscuous mode
[ 23.767873] br-br173: port 2(wlan173_2) entered blocking state
[ 23.773616] br-br173: port 2(wlan173_2) entered forwarding state
[ 23.813197] br-br173: port 2(wlan173_2) entered disabled state
[ 23.899171] br-br173: port 2(wlan173_2) entered blocking state
[ 23.899226] br-br173: port 2(wlan173_2) entered forwarding state
[ 24.287194] br-br173: port 3(wlan173) entered blocking state
[ 24.287246] br-br173: port 3(wlan173) entered disabled state
[ 24.291980] ath11k c000000.wifi wlan173: entered allmulticast mode
[ 24.297886] ath11k c000000.wifi wlan173: entered promiscuous mode
[ 24.304429] ath11k c000000.wifi wlan173: left allmulticast mode
[ 24.309737] ath11k c000000.wifi wlan173: left promiscuous mode
[ 24.315634] br-br173: port 3(wlan173) entered disabled state
[ 24.365400] br-br173: port 3(wlan173) entered blocking state
[ 24.365449] br-br173: port 3(wlan173) entered disabled state
[ 24.370197] ath11k c000000.wifi wlan173: entered allmulticast mode
[ 24.376068] ath11k c000000.wifi wlan173: entered promiscuous mode
[ 24.383156] ath11k c000000.wifi wlan173: left allmulticast mode
[ 24.387942] ath11k c000000.wifi wlan173: left promiscuous mode
[ 24.393776] br-br173: port 3(wlan173) entered disabled state
[ 24.447060] br-br173: port 3(wlan173) entered blocking state
[ 24.447100] br-br173: port 3(wlan173) entered disabled state
[ 24.451840] ath11k c000000.wifi wlan173: entered allmulticast mode
[ 24.457666] ath11k c000000.wifi wlan173: entered promiscuous mode
[ 24.463527] br-br173: port 3(wlan173) entered blocking state
[ 24.469586] br-br173: port 3(wlan173) entered forwarding state
[ 24.883421] nss-dp 3a001a00.dp6 wan: PHY Link up speed: 1000
[ 24.883829] br-br173: port 1(wan.173) entered blocking state
[ 24.888181] br-br173: port 1(wan.173) entered forwarding state
[ 31.843087] l11: disabling
[ 74.253151] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 5
[ 168.645289] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 10
[ 196.244945] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 4
[ 973.354122] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 2
[ 2334.211752] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 22
[ 3916.581028] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 7
[63276.173673] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 59
[63878.232294] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3
[65180.527662] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 675
[65211.417089] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 8
[65216.686973] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 243
[77294.133479] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[81373.575723] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 49
[81396.687501] ath11k c000000.wifi: failed to transmit frame -12
[81396.687591] ath11k c000000.wifi: failed to transmit frame -12
[81396.693588] ath11k c000000.wifi: failed to transmit frame -12
[81477.479502] ath11k c000000.wifi: failed to transmit frame -12
[81477.479608] ath11k c000000.wifi: failed to transmit frame -12
[81477.486022] ath11k c000000.wifi: failed to transmit frame -12
[81477.491275] ath11k c000000.wifi: failed to transmit frame -12
[81477.497150] ath11k c000000.wifi: failed to transmit frame -12
[81477.502859] ath11k c000000.wifi: failed to transmit frame -12
[81688.689771] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 19
[81688.701334] ath11k c000000.wifi: failed to transmit frame -12
sorry I missed your email.
I tried with stable versions: 24.10 and snapshot, and now also with 24.10.1, but it's the same (maybe a little less, but it happens the same)
Thank you... If you need, I will send you a log screen tomorrow
Are you seeing this on any of your units ? I just looked at the gl-b3000 devices I have running, the 2 main units have been up for +3 weeks and I do not see this in any of the logs of all 5 units.
maybe GL is on the right side of this one instead of the odd duck us usual
interesting. I don't think I've seen this since the patch i mentioned. Thats what gave me the impression it was fixed. I will dedicate a few units to confirm it, but I am not seeing this on gl-b3000 on the 3 units in the shop. I will check the other 2 at home again this evening
I had one unit loose connectivity a few weeks ago but I will testing on that unit the night before but i just attributed it to the testing and rebooted without checking the logs.
This may be a stretch but that fact i am not seeing this nor does @dr-m, I don't think its a GL ..thing, I am pretty sure this is pure coincidence. But could this be setup related ? ..ie mesh seems to be the go to setup for these devices and what most are using. I don't do mesh .. and haven't during development and testing at all. Looking back in the dev thread, myself and a few others provided logs of 30+ days with no or very little sign of the log pollution and or dropping connection.
I haven't confirmed anything but i did notice that the ones that provided logs, absence of this error did not seem to be running a mesh setup ..
Perhaps its the mesh setup ... or more specifically something in the setup that is making the driver unhappy ??
as i said, this may be totally far fetched but i thought it may be worth the mention.
Hi! I just checked my dmesg after 24 days of uptime (still the same firmware that I mentioned 23 days ago). There have been some ath11k messages like the following, occasionally with days in between:
[596159.115640] Ignoring NSS change in VHT Operating Mode Notification from de:39:b3:76:fd:79 with invalid nss 2
[596751.385189] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[596786.824918] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3
[598984.888271] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 9
[599011.843258] Ignoring NSS change in VHT Operating Mode Notification from de:39:b3:76:fd:79 with invalid nss 2
[602879.259356] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3
[604093.170407] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
