From: "Timur Kristóf" <timur.kristof@gmail.com>
To: ath10k@lists.infradead.org
Subject: Frequent ath10k crashes with QCA6174 on kernels 4.16 and 4.17
Date: Tue, 29 May 2018 11:52:15 +0300 [thread overview]
Message-ID: <c92e04d5b80af2a640ab97efce32d987ffb27ffe.camel@gmail.com> (raw)
Hi,
I'm experiencing a lot of ath10k driver crashes on both 4.16 (as
shipped in Fedora) and 4.17 (tried rc5 and rc6) using a Dell XPS 13
9370 with a QCA6174.
With 4.16 the driver crash always results in the whole system hanging.
With 4.17 it does not always hang the system completely, but it still
happends. I also tried to upgrade the firmware which also reduces the
frequency of the crashes but does not eliminate them completely.
The common pattern I see in dmesg is this:
[30372.900832] wlp2s0: AP 64:7c:34:3f:c3:b0 changed bandwidth, new config is 2437 MHz, width 2 (2447/0 MHz)
Searching a bit in kernel sources, this message is printed by this line:
https://github.com/torvalds/linux/blob/master/net/mac80211/mlme.c#L364
And width 2 seems to correspond to NL80211_CHAN_WIDTH_40 here:
https://github.com/torvalds/linux/blob/master/include/uapi/linux/nl80211.h#L3880
So it seems that either the driver or the firmware can't cope with it when the AP changes the bandwidth.
Here is the Fedora bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1577106
Is there anything that can be done to improve the stability of ath10k on this system?
I see there is a lot going on in the upstream repo, but not sure which branch to try: ath-next or qca?
Best regards,
Tim
ps. I'm not on the mailing list, please add me to CC when you reply. Thanks.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2018-05-29 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 8:52 Timur Kristóf [this message]
2018-05-29 10:21 ` Frequent ath10k crashes with QCA6174 on kernels 4.16 and 4.17 Kalle Valo
2018-05-29 12:32 ` Timur Kristóf
2018-05-29 13:29 ` Kalle Valo
2018-05-29 19:36 ` Timur Kristóf
2018-05-30 7:15 ` Timur Kristóf
2018-06-08 18:37 ` Ryan Hsu
2018-06-08 19:27 ` timur.kristof
2018-06-08 20:25 ` Ryan Hsu
2018-06-09 12:56 ` Timur Kristóf
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=c92e04d5b80af2a640ab97efce32d987ffb27ffe.camel@gmail.com \
--to=timur.kristof@gmail.com \
--cc=ath10k@lists.infradead.org \
/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