archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <>
To: Kalle Valo <>
Cc: ath11k <>,
	"" <>,
	netdev <>,
	LKML <>,
	Linux kernel regressions list <>
Subject: [regression] Bug 217286 - ath11k:deny assoc request, Invalid supported ch width and ext nss combination
Date: Sat, 8 Apr 2023 13:52:52 +0200	[thread overview]
Message-ID: <> (raw)

Hi, Thorsten here, the Linux kernel's regression tracker.

I noticed a regression report in 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 :

> 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.

[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v5.15..v6.2
#regzbot title: net: wireless: association is rejected by AP
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
If I did something stupid, please tell me, as explained on that page.

[1] because tells users upon registration their
"email address will never be displayed to logged out users"

             reply	other threads:[~2023-04-08 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08 11:52 Linux regression tracking (Thorsten Leemhuis) [this message]
2023-04-17  9:33 ` [regression] Bug 217286 - ath11k:deny assoc request, Invalid supported ch width and ext nss combination Thorsten Leemhuis
2023-04-17  9:50   ` Linux regression tracking (Thorsten Leemhuis)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).