[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f84c39ed-b8d8-7d0c-0eff-c90feaf5ab4f@leemhuis.info>
Date: Mon, 17 Apr 2023 11:33:49 +0200
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: P Praneesh <ppranees@...eaurora.org>,
Ganesh Sesetti <gseset@...eaurora.org>,
Sathishkumar Muruganandam <murugana@...eaurora.org>
Cc: ath11k <ath11k@...ts.infradead.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux kernel regressions list <regressions@...ts.linux.dev>,
Kalle Valo <kvalo@...nel.org>,
Jouni Malinen <jouni@...eaurora.org>
Subject: Re: [regression] Bug 217286 - ath11k:deny assoc request, Invalid
supported ch width and ext nss combination
On 08.04.23 13:52, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developers don't keep an eye on it, I decided to forward it by mail.
>
> Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
> not CCed them in mails like this.
>
> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217286 :
>
>> Built and installed v6.2 kernel (with ath11k_pci) on arm64 hardware
>> running Ubuntu22.04. Hardware has both Atheros QCN9074 module and Intel
>> AX210 module. Running each (separately) in station mode and try to
>> connect to Synology router with WiFi Access Point based on QCN9074.
>> AX210 has no problem connecting to AP but Atheros is successfully
>> authenticating but association is rejected by AP with this error message:
>>
>>
>> wlan: [0:I:ANY] [UNSPECIFIED] vap-0(wlan100): [04:f0:21:a1:7c:3e]deny assoc request, Invalid supported ch width and ext nss combination
>>
>> Please note that when running v5.15.5 kernel (with ath11k_pci), I am
>> able to connect to the same AP without problems.
>>
>> Detailed logs follow:
>> [...]
>
> See the ticket for more details.
FWIW, the reporter bisected the regression down to
552d6fd2f2 ("ath11k: add support for 80P80 and 160 MHz bandwidth")
Authored by P Praneesh, Ganesh Sesetti, and Sathishkumar Muruganandam,.
all of which I added to the list of recipients (just like Jouni Malinen,
who handled the patch). Could one of you please look into this?
While at it, let me update the tracking status:
#regzbot introduced: 552d6fd2f2
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
Powered by blists - more mailing lists