24.10rc7, TP-EAP245, error log. ath10k

Installing and Using OpenWrt
1

I am running 24.10 rc7 on TP-Link EAP245 v1, and I noted the following warnings/errors. #ath10k

Sat Feb  1 00:11:38 2025 kern.warn kernel: [ 6047.140380] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:38 2025 kern.warn kernel: [ 6047.242474] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:38 2025 kern.warn kernel: [ 6047.344865] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:38 2025 kern.warn kernel: [ 6047.447597] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:38 2025 kern.warn kernel: [ 6047.549670] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:38 2025 kern.warn kernel: [ 6047.652389] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6047.754801] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6047.857174] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6047.959577] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.061978] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.164360] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.266771] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.369182] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.471302] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.573763] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:39 2025 kern.warn kernel: [ 6048.676094] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6048.778576] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6048.881000] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6048.983302] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.085716] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.188109] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.290509] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.393154] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.495553] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.597965] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:40 2025 kern.warn kernel: [ 6049.700365] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6049.802791] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6049.904917] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.007315] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:41 2025 kern.err kernel: [ 6050.045125] ath10k_pci 0000:00:00.0: Cannot communicate with firmware, previous wmi cmds: 36954:574706 36904:574705 36904:574703 36954:574700, jiffies: 575008, attempting restart restart firmware, dev-flags: 0 x142
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.064959] ath10k_pci 0000:00:00.0: failed to transmit management frame via WMI: -11
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.073902] ath10k_pci 0000:00:00.0: failed to send wmi nop: -143
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.080300] ath10k_pci 0000:00:00.0: could not request stats (type -268435456 ret -143 specifier 1)
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.090116] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request: -143
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.098509] ath10k_pci 0000:00:00.0: removing peer, cleanup-all, deleting: peer 6b4b42bb vdev: 0 addr: b0:4e:26:2e:36:7f
Sat Feb  1 00:11:41 2025 kern.warn kernel: [ 6050.109997] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sat Feb  1 00:11:41 2025 kern.info kernel: [ 6050.249373] ieee80211 phy0: Hardware restart was requested
Sat Feb  1 00:11:42 2025 kern.warn kernel: [ 6051.224990] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Sat Feb  1 00:11:42 2025 kern.info kernel: [ 6051.242499] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
Sat Feb  1 00:11:42 2025 kern.info kernel: [ 6051.248974] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424  sw-crypt: 0 ct-sta: 0'
Sat Feb  1 00:11:42 2025 kern.info kernel: [ 6051.257544] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 24984 iram: 38672'
Sat Feb  1 00:11:42 2025 kern.warn kernel: [ 6051.329370] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Sat Feb  1 00:11:42 2025 kern.info kernel: [ 6051.344357] ath10k_pci 0000:00:00.0: rts threshold -1
Sat Feb  1 00:11:42 2025 kern.info kernel: [ 6051.357690] ath10k_pci 0000:00:00.0: device successfully recovered

Is this a firmware or driver issue?

ieee80211 phy0: Hardware restart was requested

chip reset or the entire device?

Thanks your for help!

2

today you discovered why there's an uptime command ...

3

Install non-ct driver and firmware.

4

:wink: 1h 52m 53s , so it certainly didnt reboot the device.

5

I saw the discussion around the driver -ct vs. non-ct.... need to read it first before asking the million questions going through my head.

Is the swap of drivers documented somewhere?

6

https://firmware-selector.openwrt.org/?version=24.10.0-rc7&target=ath79%2Fgeneric&id=tplink_eap245-v1

click the customize arrow, put a - in front of kmod-ath10k-ct and ath10k-firmware-qca988x-ct, add kmod-ath10k plus ath10k-firmware-qca988x to the list of packages, and request a build.

sysupgrade using the built sysupgrade image.

2 Likes
7

Thats first thing to try, just search forum for your SWBA

1 Like
8

any known downsides of using the non-ct driver?

9

I always used them, if I remember correctly, on my two Archer C2600 APs.

No issues, rock stable, but they got replaced 2 years ago, a lot of water under the bridge since then.

10

this is a little bit #offtopic, but since I am customizing my image anyway, can I remove dnsmasq, firewall4, odhcp6c, odhcpd-ipv6only from the package list or will this somehow break the boot? I am not intending to use any of the packages (in my "dump AP")

11

some of the stuff you keep have dependencies, and might not let them be removed.

if you don't need the extra space, leave them in, imho.

and yes, if you remove the wrong package, you might actually soft brick the device, by killing the network.

12

ok, I am giving this a try. thanks for your help (never used the custom image builder before - amazing!)

1 Like
13

might want to reset during flash, the config might not work between ct and non-ct drivers.

14

Thanks for the hint. Then, this is something I try on the weekend, not now...

15

I tried with non -ct package (kmod, ath10k, etc...) and attended-sysupgrade, without success.

Wifi 5GHz is not available.