Read literally just a few replies back in this thread: here, here, here, here . This is a known ath11k bug.
I've been disabling all wireless before flashing a new sysupgrade to work around it until a PR to fix it is committed.
1 Like
Would stopping wpad allow for attended sysupgrade? It's not working for me?
Yes. That's exactly what needs to happen.
After resetting 2x, I finally managed to get the newer snapshot showing the correct version and the kernel too updated.
One thing that I have noted is that the 160MHz channel width has disappeared in this snapshot.
I disabled both wifi SSIDs in wireless and I am still unable to perform an attended sysudate. Same package errors show up
Try a channel from 100 to 128
I have currently snapshot r22322 on channel 36 a width of 160 MHz.
attended sysupgrade will not work currently due to some package issues... started with yesterday's snapshot updates. Give it a couple of days and those packages should be rebuilt and start working again.
But stopping wpad (system > startup > wpad STOP) prior to flashing is the appropriate step.
4 Likes
Packages are rebuilt and working now - so you should be able to complete your update.
2 Likes
Yep! I was able to attended sysupgrade without issue!
2 Likes
Just upgraded to r22392 vis AttendedSysUpgrade
Some issues:
- Wifi (5G only) do not come up after upgrade
- After remove, and add it back, connect speed is 54/54Mbps (as reported by Windows Link speed), speed test only has 27Mbps .
Totally normal here. Check settings, or do a reflash w/o retaining settings.
After reboot and check:
- After Wifi SSID is added back, the Wifi Type is BLANK in Luci. After setting it to AX, then set to 80MHz, it is back to normal.
- For 2.4GHz radio, the default transmission power is 5dbm. I need to change it manually.
1 Like
Anyone noticed IPv6 problems in latest snapshots r22392 - r22396? Router gets IPv6 but it doesnt reach lan clients.
edit : Clean install or not, can't get IPv6 working properly with r22392 - r22396. Went back to r22260 and now clients get IPv6.
I have pretty consistently been getting firmware crashes when a WPA3 802.11r connected (FT-SAE) device disconnects, when it is roaming(?)
The error has been identical both times, starting with the WPA3 FT roaming client device disconnecting:
Sat Mar 25 11:53:34 2023 daemon.notice hostapd: phy0-ap2: AP-STA-DISCONNECTED a8:cc:6f:0a:50:f1
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848]
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] ar_wal_peer.c:2462 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] Thread ID : 0x00000069 Thread name : WLAN RT0 Process ID : 0
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] Register:
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] SP : 0x4c115f48
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] FP : 0x4c115f50
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] PC : 0x4b195a10
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] SSR : 0x00000008
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] BADVA : 0x00020000
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] LR : 0x4b1951ac
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848]
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] Stack Dump
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] from : 0x4c115f48
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848] to : 0x4c1167a0
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.621848]
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.670474] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.692720] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Sat Mar 25 11:53:34 2023 kern.err kernel: [10758.700863] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Sat Mar 25 11:53:34 2023 kern.info kernel: [10758.733468] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.006448] ath11k c000000.wifi: failed to find peer a8:cc:6f:0a:50:f1 on vdev 2 after creation
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.006499] ath11k c000000.wifi: failed to find peer vdev_id 2 addr a8:cc:6f:0a:50:f1 in delete
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.013963] ath11k c000000.wifi: failed peer a8:cc:6f:0a:50:f1 delete vdev_id 2 fallback ret -22
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.022669] ath11k c000000.wifi: Failed to add peer: a8:cc:6f:0a:50:f1 for VDEV: 2
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.031677] ath11k c000000.wifi: Failed to add station: a8:cc:6f:0a:50:f1 for VDEV: 2
Sat Mar 25 11:53:34 2023 daemon.notice hostapd: phy0-ap1: STA a8:cc:6f:0a:50:f1 IEEE 802.11: Could not add STA to kernel driver
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.086715] ath11k c000000.wifi: failed to update rx tid queue, tid 0 (-108)
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.086742] ath11k c000000.wifi: failed to update reo for rx tid 0: -108
Sat Mar 25 11:53:34 2023 kern.info kernel: [10759.092821] phy0-ap2: HW problem - can not stop rx aggregation for a8:cc:6f:0a:50:f1 tid 0
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.099529] ath11k c000000.wifi: failed to update rx tid queue, tid 0 (-108)
Sat Mar 25 11:53:34 2023 kern.warn kernel: [10759.107589] ath11k c000000.wifi: failed to update reo for rx tid 7: -108
Sat Mar 25 11:53:34 2023 kern.info kernel: [10759.114783] phy0-ap2: HW problem - can not stop rx aggregation for a8:cc:6f:0a:50:f1 tid 7
Sat Mar 25 11:53:35 2023 kern.warn kernel: [10759.156470] ath11k c000000.wifi: failed to send WMI_PEER_DELETE cmd
Sat Mar 25 11:53:35 2023 kern.warn kernel: [10759.156537] ------------[ cut here ]------------
PS.
I have been testing assigning ath11k IRQ affinities statically, and that seems stable. I have left ceXX and the edma IRQs to core0, but have assigned the others. But trying WPA3 802.11r (with a device actually using it) quickly causes the crash.
4 Likes
Thank you for all your efforts @hnyman . As always I look up to your knowledge.
@hnyman like how quickly? at the first disconnect? randomly?
this really seems a case for a fw bug... (but the main problem is that currently we are stuck a 2.5.0 due to regdb problems)
I was going to pick up one of these routers, but from reading this it seems like a bug fest.
OK after finding this. https://github.com/openwrt/openwrt/pull/12235 it
Seems like the sysupgrade bug will be fixed. Thanks to @slh for the info and @Ansuel for the patch.
1 Like
the sysupgrade patch is well known but no idea it was that present... we already have an idea... just I need to understand a """"not-so-shit"""" solution to it...
But i think it will be a mix of killing wpad + my patch
@hnyman there might be a patch to backport... will tag you to test it directly in the pr
1 Like
Nah… it’s not that bad, just having some of the quirks ironed out. 
it’ll get there. Depending on one’s use case… vanilla users should find it to be very stable and relatively set and forget.