From: Kalle Valo <kvalo@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: Cedric Veilleux <veilleux.cedric@gmail.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [REGRESSION] ath10k: failed to flush transmit queue
Date: Wed, 31 Jul 2024 21:13:23 +0300 [thread overview]
Message-ID: <87le1hjupo.fsf@kernel.org> (raw)
In-Reply-To: <1df0c5cc-ce58-450e-9f91-7f8f599cb11d@nbd.name> (Felix Fietkau's message of "Fri, 12 Jul 2024 10:08:10 +0200")
Felix Fietkau <nbd@nbd.name> writes:
> On 12.07.24 04:23, Cedric Veilleux wrote:
>
>> AP mode.
>> Both 2.4 and 5ghz channels.
>> Using WLE600VX (QCA986x/988x), we are seeing the following errors in
>> kernel logs:
>> [12978.022077] ath10k_pci 0000:04:00.0: failed to flush transmit
>> queue
>> (skip 0 ar-state 1): 0
>> [13343.069189] ath10k_pci 0000:04:00.0: failed to flush transmit queue
>> (skip 0 ar-state 1): 0
>> They are somewhat random but frequent. Can happen once a day or many
>> times per hour.
>> They are associated with 3-4 seconds of radio silence. Full packet
>> loss. Then everything resumes normally, STA are still associated and
>> traffic resumes.
>> I have tested with major kernel versions:
>> 6.1.97: stable (tested for many days on 10+ access points)
>> 6.2.16: stable (tested for few hours single machine)
>> 6.3.13: stable (tested for few hours single machine)
>> 6.4.16: unstable (we have errors within an hour)
>> 6.5.13: unstable (we have errors within an hour)
>> 6.6.39: unstable (we have errors within an hour)
>> 6.7.12: unstable (we have errors within an hour)
>> 6.8.10: unstable (we have errors within an hour)
>> 6.9.7: unstable (we have errors within an hour)
>> From these tests I believe something changed in 6.4 series causing
>> instabilities and the dreaded "failed to flush transmit queue" error.
>> This is a custom linux distribution. Only change is the kernel. All
>> other packages are same versions. Everything rebuilt from source using
>> bitbake/yocto. Same linux-firmware files.
>
> I'm pretty sure it's caused by this commit:
>
> commit 0b75a1b1e42e07ae84e3a11d2368b418546e2bec
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Fri Mar 31 16:59:16 2023 +0200
>
> wifi: mac80211: flush queues on STA removal
>
> I guess somebody needs to look into making the queue flush on ath10k
> more reliable (or even better, implement a more lightweight .flush_sta
> op).
>
> I don't have time to do the work myself, but hopefully this
> information could help somebody else take care of it.
Adding ath10k list so that everyone see this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-07-31 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 2:23 [REGRESSION] ath10k: failed to flush transmit queue Cedric Veilleux
2024-07-12 8:08 ` Felix Fietkau
2024-07-31 18:13 ` Kalle Valo [this message]
2025-02-20 13:55 ` James Prestwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87le1hjupo.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=veilleux.cedric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).