From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Liang <stephenliang7@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: QCA6390 on Dell XPS 13 and kernel crashes
Date: Wed, 09 Dec 2020 17:09:28 +0200 [thread overview]
Message-ID: <87v9db9ftj.fsf@codeaurora.org> (raw)
In-Reply-To: <CAE+mCOEX5ccBa2HBYpi_3YpayApyr-C1csBpvvjWZ-hnW38Oqw@mail.gmail.com> (Stephen Liang's message of "Wed, 2 Dec 2020 15:49:39 -0800")
Stephen Liang <stephenliang7@gmail.com> writes:
> For reference, I am running Fedora Rawhide kernel 5.10.0-0.rc6 with
> commit 59c6d022df8efb450f82d33dd6a6812935bd022f and a revert of
> 7fef431be9c9 patched in.
>
> I am able to connect to WiFi and did not receive any immediate
> freezing, hard kernel panics, etc. Uptime is now going on 35 minutes
> and able to get 50 up/down throughput.
Thanks, good to know. On what platform is this, can you share more
details? Is it the new Dell XPS 13 9310 or something else?
> I do see a number of taints in dmesg while connecting to an access
> point but the taint doesn't seem to affect functionality, for example:
> https://pastebin.com/raw/gbzuvs3q
This commit should fix that:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath11k-qca6390-bringup&id=fa4eea695afb286ae38beb30dabf251335cb4a62
I recommend using ath11k-qca6390-bringup branch, it has quite a few
fixes:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=ath11k-qca6390-bringup
> Finally, rebooting the computer does require a hard power down.
You mean that the reboot stalls and you need to turn off the laptop
using power button?
--
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-09 15:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 23:49 Re: ath11k: QCA6390 on Dell XPS 13 and kernel crashes Stephen Liang
2020-12-09 15:09 ` Kalle Valo [this message]
2020-12-10 3:07 ` Stephen Liang
2020-12-10 7:37 ` Stephen Liang
-- strict thread matches above, loose matches on Subject: below --
2020-12-06 17:38 Mitchell Nordine
2020-12-06 17:53 ` wi nk
2020-12-06 21:45 ` wi nk
2020-12-07 1:17 ` wi nk
2020-12-07 14:45 ` Mitchell Nordine
2020-12-07 17:01 ` wi nk
2020-12-09 1:52 ` wi nk
2020-12-09 9:43 ` wi nk
2020-12-09 15:28 ` wi nk
2020-12-09 15:35 ` Kalle Valo
2020-12-09 15:39 ` wi nk
2020-12-09 15:50 ` wi nk
2020-12-09 15:50 ` Kalle Valo
2020-12-09 15:55 ` wi nk
2020-12-09 21:46 ` wi nk
2020-12-11 12:28 ` wi nk
2020-12-12 5:37 ` Kalle Valo
2020-12-12 11:46 ` wi nk
2020-12-12 23:29 ` wi nk
2020-12-13 0:03 ` wi nk
2020-12-13 0:59 ` Mitchell Nordine
2020-12-13 22:09 ` Stephen Liang
2020-12-16 8:50 ` Kalle Valo
2020-11-30 16:55 Kalle Valo
2020-11-30 17:02 ` wi nk
2020-12-01 10:17 ` wi nk
2020-12-05 19:17 ` wi nk
2020-12-06 8:05 ` wi nk
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=87v9db9ftj.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=stephenliang7@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