From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: James Prestwood <prestwoj@gmail.com>,
Baochen Qiang <quic_bqiang@quicinc.com>,
<ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath10k: poll service ready message before failing
Date: Wed, 28 Feb 2024 13:31:30 -0800 [thread overview]
Message-ID: <18ab7c1e-daa0-498d-ae01-d34784199474@quicinc.com> (raw)
In-Reply-To: <6362d9b2-6ed2-4454-bf1b-8614d181bc93@gmail.com>
On 2/28/2024 10:46 AM, James Prestwood wrote:
> This does appear to have fixed it! For reference this was my test:
>
> for i in $(seq 1 100000); do sudo ip link set wlan0 down; sudo ip link
> set wlan0 up; echo $?; done
>
> I never saw the up command fail, and after a while I noticed one of the
> iterations took a bit longer to complete. Checked dmesg and saw:
>
> [ 1006.017198] ath10k_pci 0000:02:00.0: failed to receive service ready
> completion, polling..
> [ 1006.017295] ath10k_pci 0000:02:00.0: service ready completion
> received, continuing normally
>
> I then started IWD and it was able to connect fine (data frames were
> being passed). I was able to trigger this 3 times relatively quickly,
> each time IWD connected afterwards. So from my end this appears fixed.
>
> You can add tested-by me if you like:
>
> Tested-By: James Prestwood <prestwoj@gmail.com> # on QCA6174 hw3.2
Thanks for the initial report and the testing :)
/jeff
next prev parent reply other threads:[~2024-02-28 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 3:17 [PATCH] wifi: ath10k: poll service ready message before failing Baochen Qiang
2024-02-21 12:38 ` James Prestwood
2024-02-22 2:18 ` Baochen Qiang
2024-02-28 18:46 ` James Prestwood
2024-02-28 21:31 ` Jeff Johnson [this message]
2024-02-26 10:45 ` Kalle Valo
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=18ab7c1e-daa0-498d-ae01-d34784199474@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@gmail.com \
--cc=quic_bqiang@quicinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).