Open MisiekDP opened 1 month ago
Invalid Version reported. `` Is this from a clean repository?
Invalid Release reported. `` Is this from a clean repository?
Invalid Target/Subtarget reported. `` Is this from a supported device?
You might want to try the latest snapshot version 26937 or newer, there are some fixes for ath11k.
Yes, snapshot will be significantly more stable based on my experience for the AX3600 vs. the 23.X branch. The OOM issue for my has been significantly reduced due to the addition of the SMP Affinity script in snapshot. You can also try running the script yourself on each reboot on 23.05.
https://github.com/openwrt/openwrt/issues/13562#issuecomment-1817573570
Wow, thanks for ideas guys @edrikk @lorand-horvath but could you tell me how to build this SNAPSHOT version with my own packages? All the time I used firmware selector with Attendedsysupgrade package but how to build SNAPSHOT?
I’m fairly sure ASU gives that option. At least in advanced mode maybe?
https://openwrt.org/docs/guide-user/installation/attended.sysupgrade
But maybe first just try running the script on your current version after a reboot.
@edrikk I can send you later screenshots from Advanced mode later. I tried yesterday using ASU but I couldn't find any options to choose SNAPSHOT.
And yea, it is good idea to try script first - could you mąybe tell me how to run this script and where? Or maybe you have any instruction for this? And how to check if this script is running? Should I get any logs of this script in Systm Log section?
@MisiekDP in the snapshot release, auc has been replaced with owut, but if I remember correctly, command should be more less: auc -c -b 23.05 -B snapshot
.
Another way is just to add desire packages on https://firmware-selector.openwrt.org/ when you click on Customize installed packages and/or first boot script
Hi boys,
For this failure:
[175506.181831] ath11k c000000.wifi: Spurious quick kickout for STA e8:db:84:e5:3c:56
[187480.659123] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 2
[189620.400508] ath11k c000000.wifi: Spurious quick kickout for STA e8:db:84:e5:3c:56
[228661.743942] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[232841.819263] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
[234274.697449] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
@qosmio in the NSS repository added this patch and the bug disappeared, the patch comes from ath-next: https://github.com/qosmio/openwrt-ipq/blob/qualcommax-6.x-nss-wifi/package/kernel/mac80211/patches/nss/ath11k/453-ath11k-flush-management-frames-to-firmware-before-wa.patch
Maybe when @robimarko or @ansuel or @PolynomialDivision (was the last contributor to the last ath-next sync in October 2023) synchronize again with ath-next this patch will be already incorporated and the bug will disappear.
Regards, Agustin
Describe the bug
When using the router (when browsing the web), crashes occur in the form of: switching off the WiFi network, disconnection of the connection. If you go through the router's logbook, you will notice all sorts of errors, including those with the message "Out of memory" and the killing of given processes. Using a package that allows the logging of component usage, it is possible to see increased RAM usage up to the time of failure. There was also a situation where, due to lack of memory, it was also impossible to log into the LUCI GUI panel (the only solution to enable WiFi was to restart the device).
Memory usage during the error:![image](https://github.com/user-attachments/assets/e4a47952-f2ce-4d3f-b2ca-a98f3ef3fbfb)
CPU usage during the error:![image](https://github.com/user-attachments/assets/9b5ef749-a64c-4808-b738-33f914e910da)
Signal quality:![image](https://github.com/user-attachments/assets/78b325a6-3697-407b-a90a-e19a12c13526)
Kernel logs:
System logs:
OpenWrt version
r23809-234f1a2efa
OpenWrt release
23.05.3
OpenWrt target/subtarget
ipq807x/generic
Device
Xiaomi AX3600
Image kind
Official downloaded image
Steps to reproduce
Actual behaviour
When using the router (when browsing the web), crashes occur in the form of: switching off the WiFi network, disconnection of the connection. If you go through the router's logbook, you will notice all sorts of errors, including those with the message "Out of memory" and the killing of given processes.
Expected behaviour
I expect stable router operation without a rash of errors.
Additional info
No response
Diffconfig
No response
Terms