From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Ryan Hsu <ryanhsu@qti.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k-regression due to "ath10k: fix napi_poll budget overflow" c9353bf483d3
Date: Fri, 27 Oct 2017 09:40:19 +0000 [thread overview]
Message-ID: <877evh53p8.fsf_-_@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <fa6e3ee2-91b5-a54b-afe3-87f30aac7a48@leemhuis.info> (Thorsten Leemhuis's message of "Sun, 8 Oct 2017 10:27:35 +0200")
+ linux-wireless
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Lo! On 03.10.2017 01:40, Ryan Hsu wrote:
>> On 10/01/2017 01:59 AM, Thorsten Leemhuis wrote:
>>> Lo! The wifi connection of my Dell XPS13 (9360) with its QCA6174
>>> sometimes suddenly stops working since I switched to 4.14-rc2+. Every
>>> time it happens, there is this error message in dmesg:
>>>> ath10k_pci 0000:3a:00.0: failed to extract amsdu: -11
>>> I have to switch wifi off and on with the hotkey to reconnect. I can
>>> trigger the aborts by starting a big download and waiting a few minutes.
>>> Sometimes the connections aborts during normal load. Installing the
>>> latest firmware didn't help. The wifi works just fine with 4.13.3. While
>>> investigating this I noticed a few messages in dmesg that only appear in
>>> 4.14-rc (I used 35dbba31be52):
>> You do run the 4.13.3 v.s 4.14-rc with the same QCA6174 firmwrae, right?
>> Just want to understand the test setup here so that I could give it
>> a try myself, and in 11ac or 11n mode you're testing?
>
> Yup, same firmware (reproduced it with
> firmware-6.bin_WLAN.RM.4.4.1-00058-QCARMSWP-1 before bisecting). And the
> problem showed up with 2g and 5g networks. But while investigating it I
> noticed the problem does not show up with all wifi routers. It happens
> with my Fritz!Box 6490 Cable and another Fritz!Box I tried, but not with
> the wifi network at work (no idea what kind of routers are installed
> there; I can try to find out if it matters).
>
>>>> 3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174
>>>> 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
>> […] Would you mind do a bisect to locate the failure, please?
>
> Did that yesterday and it turned out it's due to commit c9353bf483d3
> (ath10k: fix napi_poll budget overflow). Reverting it on top of linux
> master from yesterday made the wifi connection stable again for me.
Sorry, I have not been able to follow this discussion very closely but
was the conclusion? Should we should revert c9353bf483d3 for 4.14 or
what? I should still have time to do that, but not much.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-27 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 8:59 ath10k-regression in 4.14: Connections aborts with "failed to extract amsdu: -11" Thorsten Leemhuis
2017-10-02 23:40 ` Ryan Hsu
2017-10-08 8:27 ` ath10k-regression due to "ath10k: fix napi_poll budget overflow" c9353bf483d3 (Was: " Thorsten Leemhuis
2017-10-16 9:04 ` ath10k-regression due to "ath10k: fix napi_poll budget overflow" c9353bf483d3 Rouven Czerwinski
2017-10-27 9:40 ` Kalle Valo [this message]
2017-10-27 19:01 ` Ryan Hsu
2017-10-29 7:44 ` Kalle Valo
2017-10-29 10:21 ` Thorsten Leemhuis
2017-10-08 9:39 ` Wifi slow on the XPS13 (9360) (QCA6174) (Was Re: ath10k-regression in 4.14: Connections aborts with "failed to extract amsdu: -11") Thorsten Leemhuis
2017-10-29 7:27 ` ath10k: Wifi slow on the XPS13 (9360) (QCA6174) Kalle Valo
2017-10-31 15:47 ` Thorsten Leemhuis
2017-11-01 7:25 ` Kalle Valo
2017-10-29 7:06 ` ath10k-regression in 4.14: Connections aborts with "failed to extract amsdu: -11" 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=877evh53p8.fsf_-_@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=ryanhsu@qti.qualcomm.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