From: Kalle Valo <kvalo@codeaurora.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Anthony Wong <anthony.wong@canonical.com>,
Stephan Fabel <stephan.fabel@canonical.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: Re: Ath10k on XPS 9380 regularly disconnects
Date: Mon, 01 Apr 2019 11:37:17 +0300 [thread overview]
Message-ID: <877ece2kaq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <BD07B681-0083-4537-87D2-099F7152C51F@canonical.com> (Kai-Heng Feng's message of "Mon, 1 Apr 2019 16:03:21 +0800")
Kai-Heng Feng <kai.heng.feng@canonical.com> writes:
> at 23:43, Kai-Heng Feng <kai.heng.feng@canonical.com> wrote:
>
>> at 01:05, Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>>> + ath10k list
>>> - netdev & linux-kernel
>>>
>>> Kai-Heng Feng <kai.heng.feng@canonical.com> writes:
>>>
>>>> There’s an issue that ath10k disconnects at regular basis [1], on
>>>> Linux kernel 4.18.
>>>>
>>>> Unfortunately I can’t reproduce the issue on XPS 9380 at my hand.
>>>>
>>>> Is there already a fix in upstream kernel?
>>>
>>> I'm not aware of any fixes related to this. Is this a regression? In
>>> other words, is there a known version of ath10k or firmware which didn't
>>> have this problem?
>>
>> We know this issue happen on kernel v4.15 and v4.18, but kernels
>> before v4.15 were not tested.
>>
>> The issue happens with Google Mesh, which has 802.11ac capability.
>>
>> I haven’t been able to reproduce the issue with an 802.11n router (yet).
>
> Do I need a special WiFi router which support RX reorder to reproduce
> the issue?
>
> It's introduced by commit c545070e404b (“ath10k: implement rx reorder
> support”).
I don't understand your question at all.
--
Kalle Valo
next prev parent reply other threads:[~2019-04-01 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 5:35 Ath10k on XPS 9380 regularly disconnects Kai-Heng Feng
2019-03-21 17:05 ` Kalle Valo
2019-03-22 15:43 ` Kai-Heng Feng
2019-04-01 8:03 ` Kai-Heng Feng
2019-04-01 8:37 ` Kalle Valo [this message]
2019-04-01 9:10 ` Kai-Heng Feng
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=877ece2kaq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=anthony.wong@canonical.com \
--cc=ath10k@lists.infradead.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stephan.fabel@canonical.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).