From: Kalle Valo <kvalo@codeaurora.org>
To: Justin Mazzola Paluska <jmp@justinmp.com>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: qca6390 firmware crashes while connecting to 160 MHz channel
Date: Fri, 12 Feb 2021 08:16:16 +0200 [thread overview]
Message-ID: <87k0rdste7.fsf@codeaurora.org> (raw)
In-Reply-To: <5fd39674-d513-c28e-5469-693d96e804c0@justinmp.com> (Justin Mazzola Paluska's message of "Thu, 11 Feb 2021 17:23:47 -0500")
Justin Mazzola Paluska <jmp@justinmp.com> writes:
> On 2/11/21 6:10 AM, Kalle Valo wrote:
>> (changing the title to find this easier)
>>
>> Justin Mazzola Paluska <jmp@justinmp.com> writes:
>>
>>> On 12/21/20 12:11 PM, Kalle Valo wrote:
>>>>> My router supports 160 MHz channels in the 5 GHz bands [1]. I
>>>>> switched the router to advertising 80 MHz channels and the card could
>>>>> connect.
>>>> Thanks for the detailed debugging, this should help us reproducing the
>>>> problem. What's the exact openwrt version you are using?
>>> The OpenWRT version is:
>>>
>>> OpenWrt 19.07.5 r11257-5090152ae3 / LuCI openwrt-19.07 branch
>>> git-20.341.57626-51f55b5
>>>
>>> (This is the latest stable release.)
>> Thanks. I got a report that this might be due to commit 3579994476b6
>> ("wireless: fix wrong 160/80+80 MHz setting"). Can you try reverting the
>> commit just to confirm we are seeing the same issue?
>
> I will try over the weekend. Shall I still use the
> ath11k-qca6390-bringup branch or something else? (I'm still running
> the ath11k-qca6390-bringup branch on my laptop).
Yes, use the same branch. Least amount of changes that way.
--
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:[~2021-02-12 6:16 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
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 [this message]
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=87k0rdste7.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=jmp@justinmp.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).