From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Liang <stephenliang7@gmail.com>
Cc: ath11k@lists.infradead.org, wi nk <wink@technolu.st>
Subject: Re: ath11k-qca6390-bringup-202012140938: rebate to v5.10 and MHI M2 workaround
Date: Wed, 16 Dec 2020 09:46:11 +0200 [thread overview]
Message-ID: <87tusmxkfw.fsf@codeaurora.org> (raw)
In-Reply-To: <CAE+mCOEavJkcsgBvLR1z=kLUEwW9jJzVvi7hoxVrkBYj=pwKSQ@mail.gmail.com> (Stephen Liang's message of "Tue, 15 Dec 2020 21:41:03 -0800")
Stephen Liang <stephenliang7@gmail.com> writes:
> Uptime has been very good so far at 24 hours, no hangs. I did see a
> backtrace when associating with a different AP, please see:
> https://pastebin.com/raw/5VTAK1mp
>
> This backtrace does not appear to affect functionality and the AP
> associates just fine.
I have seen the same lockdep warning. Our current thinking is that it's
just a false warning, but we need to do more analysis before submit a
patch to silence the warning.
> Speedtest.net is giving me 340 mbps down / 185 mbps up, so very good
> throughput. I can do a LAN iperf throughput test later on as well if
> there's interest.
>
>> * name of the bringup branch tag you used
>
> ath11k-qca6390-bringup-202012140938
>
>> * if there are other changes in the kernel, patches, reverts etc
>
> Clean copy of Fedora rawhide kernel 5.10.0-0.rc6.20201202git509a15421674.91
>
>> * do you use the memmap kernel parameter
>
> No
>
>> * make and model of the laptop/computer (eg. Dell XPS 13 9310)
>
> Dell XPS 9310
>
>> * how much testing you did
>
> Mixed usage, suspend, wake, charge, discharge, etc. WiFi network
> disassociate and associate, etc.
Thank you for the report, good to hear that it's working.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-12-16 7:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 9:56 ath11k-qca6390-bringup-202012140938: rebate to v5.10 and MHI M2 workaround Kalle Valo
2020-12-14 12:28 ` Thomas Krause
2020-12-16 7:40 ` Kalle Valo
2020-12-14 16:51 ` wi nk
2020-12-16 5:41 ` Stephen Liang
2020-12-16 7:46 ` Kalle Valo [this message]
2020-12-18 21:27 ` Justin Mazzola Paluska
2020-12-19 16:44 ` Justin Mazzola Paluska
2020-12-19 21:46 ` Justin Mazzola Paluska
2020-12-21 17:11 ` Kalle Valo
2020-12-21 19:25 ` Justin Mazzola Paluska
2021-02-11 11:10 ` ath11k: qca6390 firmware crashes while connecting to 160 MHz channel Kalle Valo
2021-02-11 22:23 ` Justin Mazzola Paluska
2021-02-12 6:16 ` Kalle Valo
2021-02-13 18:36 ` Justin Mazzola Paluska
2021-03-01 7:21 ` Wen Gong
2021-03-01 7:54 ` Kalle Valo
2021-03-01 10:37 ` Wen Gong
2021-03-01 10:55 ` Kalle Valo
2021-05-19 4:14 ` Wen Gong
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=87tusmxkfw.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=stephenliang7@gmail.com \
--cc=wink@technolu.st \
/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