Cryptic status message from ath10k

Installing and Using OpenWrt
1

I just updated one of my x64 devices to the latest release (23.05.5). Everything's working great, but there's this message that keeps popping up on the console (below, [Timestamp] refers to the actual time since boot):

[Timestamp] ath10k_pci 0000:02:00.0: received bcn tmpl tx status on vdev 0: 3

The message appears at irregular intervals (the average for the last couple of dozen is 491 seconds with standard deviation of 364).

The 0000:02:00.0 device, per lspci, is:

02:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31)

I tried looking this up on the Interwebs, but the error description is so full of shortened words that searches didn't produce anything relevant.

Possibly relevant: my office is in an industrial building, so the airwaves are heavily congested (lots of wireless networks around). Also, right now, the device is on my workbench, in close proximity to several other Wi-Fi devices. So if this message signifies interference problems, I totally understand where the interference comes from. In fact, I've had other devices experience stuck beacon errors on this workbench...

So the question is, what does this message actually say?

2

It counts retransmit if it waits too long for txop

3

received bcn tmpl tx status on

Can often get some hints by searching the driver source for the largest part of the message that doesn't change in a way that doesn't break up the pieces. Same for Google you could search for "received bcn tmpl tx status on", note the double quotes which tell Google the words must appear together.

4

Did that before posting; the search returned four results, all links to code repositories or related mail lists where this message appears in code. Interestingly, this one:

https://lists.infradead.org/pipermail/ath10k/2014-December/004000.html

comes under the heading "ath10k: implement new beacon tx status event". I wonder if this is my old friend the stuck beacon error under a different name...

Meanwhile, I have relocated the device away from the cursed workbench. Right now, uptime is 22 minutes; the console is error-free (to remind, on the workbench, the error occurred, on average, every 8 minutes). So I am guessing, the error is interference-related...