I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:

[root(a)fw01 ~]# modinfo ath10k_pci
filename:       /lib/modules/6.6.47-ipfire/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
firmware:       ath10k/QCA9377/hw1.0/board.bin
firmware:       ath10k/QCA9377/hw1.0/firmware-5.bin
firmware:       ath10k/QCA9377/hw1.0/firmware-6.bin
firmware:       ath10k/QCA6174/hw3.0/board-2.bin
firmware:       ath10k/QCA6174/hw3.0/board.bin
…
parm:           irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
…

This is most likely because of updating the firmware for your card.

-Michael

> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
> 
> Hi,
> 
> since some time I noticed strange messages according to my WLAN card.
> With CU189 these are very frequently.
> 
> An extract from now:
> 
> ...
> Oct 16 16:09:17 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to increase tx pending count: -16, dropping
> Oct 16 16:10:39 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to increase tx pending count: -16, dropping
> Oct 16 16:11:20 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:13:45 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to increase tx pending count: -16, dropping
> Oct 16 16:18:47 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:18:52 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:13 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:28 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:33 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:38 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:43 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:48 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:54 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:19:59 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:20:04 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:20:09 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:20:24 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:20:40 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:21:10 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:21:16 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:21:41 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:21:46 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> Oct 16 16:21:51 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
> ............
> 
> Regards,
> Bernhard
> 
> BTW: I'm missing the status part of the hostapd WUI page.