From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "regressions@leemhuis.info" <regressions@leemhuis.info>,
"Greenman, Gregory" <gregory.greenman@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"chiluk@ubuntu.com" <chiluk@ubuntu.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211
Date: Thu, 1 Dec 2022 11:33:34 +0000 [thread overview]
Message-ID: <2026016246ef719605c9932feeb56b105833593b.camel@intel.com> (raw)
In-Reply-To: <14722778-dda0-cb9f-8647-892493d94a5c@leemhuis.info>
On Thu, 2022-12-01 at 11:14 +0100, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker.
>
> Luca, I noticed a regression report in bugzilla where I'd like your
> advice on. To quote https://bugzilla.kernel.org/show_bug.cgi?id=216753
Hi Thorsten wearing-the-regression-hat, 🙂
I'm not the maintainer of iwlwifi anymore, so I'm adding the new
maintainer here, Gregory Greenman.
Gregory, can you take a look?
> > It looks like the self-managed regulatory information is causing the 6ghz band to be disabled on my AX211 (in the US).
> > iw reg get shows no 6ghz bands (output at the bottom).
> >
> > $ sudo iw phy0 channel
> > ...
> > Band 4:
> > * 5955 MHz [1] (disabled)
> > * 5975 MHz [5] (disabled)
> > * 5995 MHz [9] (disabled)
> > ....(continues with all disabled
> > * 7115 MHz [233] (disabled)
> > ...
> >
> > I was able to narrow this down to having been introduced during the 5.16 development window, as 5.15.79 linux-stable kernel works and the 5.16.12 does
> > not (earlier builds of 5.16 kernel fail to boot on my machine for some reason).
> >
> > I found https://community.frame.work/t/kernel-5-16-6ghz-disabled-ax210/15675/5
> > and they imply that this regression was introduced by
> > 698b166ed3464e1604a0e6a3e23cc1b529a5adc1
> > I haven't independently verified this commit as the definitive issue.
>
> You authored 698b166ed346 ("iwlwifi: mvm: read 6E enablement flags from
> DSM and pass to FW"). As it is a regressions is ideally should be dealt
> with. But this area in tricky due to the legal implications. Hence I
> wonder: is there anything we can do about this, or is this simply a case
> where we have to bite the bullet and live with this regression?
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
next prev parent reply other threads:[~2022-12-01 11:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 10:14 [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211 Thorsten Leemhuis
2022-12-01 11:33 ` Coelho, Luciano [this message]
2022-12-02 15:37 ` Dave Chiluk
2022-12-02 16:02 ` Thorsten Leemhuis
2022-12-02 16:46 ` Marcel Holtmann
2022-12-02 17:18 ` Dave Chiluk
2022-12-02 17:42 ` Maxime Bizon
2022-12-04 9:37 ` Thorsten Leemhuis
2022-12-20 13:16 ` Maxime Bizon
2023-01-03 19:48 ` Dave Chiluk
2022-12-02 17:46 ` Marcel Holtmann
2022-12-05 16:35 ` Dave Chiluk
2023-01-03 17:37 ` Dave Chiluk
2023-01-04 8:50 ` Coelho, Luciano
2023-01-05 6:15 ` Greenman, Gregory
2023-01-06 15:37 ` Dave Chiluk
2023-01-19 14:09 ` Greenman, Gregory
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=2026016246ef719605c9932feeb56b105833593b.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=chiluk@ubuntu.com \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.