From: Bjorn Helgaas <helgaas@kernel.org>
To: Mukesh Sisodiya <mukesh.sisodiya@intel.com>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
Kalle Valo <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Significant WiFi Speed Reduction with Kernel Versions > 6.8.12 on Intel Wi-Fi 6 AX203
Date: Tue, 25 Feb 2025 12:25:14 -0600 [thread overview]
Message-ID: <20250225182514.GA512422@bhelgaas> (raw)
In-Reply-To: <8e9c5c74-9b36-48bb-b74a-9a209b71a634@leemhuis.info>
On Thu, Aug 08, 2024 at 08:43:53AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 07.08.24 11:12, Linux regression tracking (Thorsten Leemhuis) wrote:
> >
> > Mukesh Sisodiya, I noticed a report about a regression in
> > bugzilla.kernel.org that appears to be caused by a change of yours:
> >
> > 099a47dbe71b75 ("wifi: iwlwifi: Add support for new 802.11be device")
> > [v6.9-rc1]
>
> For the record, turns out the bisection went a bit sideways and the
> problems apparently is caused by 84ec2d2e960f33 ("wifi: iwlwifi: disable
> 160 MHz based on subsystem device ID") [v6.9-rc1]. For details, see
> https://bugzilla.kernel.org/show_bug.cgi?id=219114#c8
Browsing the regression tracker, this seems stalled with no responses
even though the submitter (bcc'd) has bisected it.
Maybe regzbot will notice the correct commit below?
#regzbot introduced: 84ec2d2e960f ("wifi: iwlwifi: disable 160 MHz based on subsystem device ID")
next prev parent reply other threads:[~2025-02-25 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 9:12 [regression] Significant WiFi Speed Reduction with Kernel Versions > 6.8.12 on Intel Wi-Fi 6 AX203 Linux regression tracking (Thorsten Leemhuis)
2024-08-08 6:43 ` Linux regression tracking (Thorsten Leemhuis)
2025-02-25 18:25 ` Bjorn Helgaas [this message]
2025-03-03 22:27 ` Bjorn Helgaas
2025-03-05 12:56 ` Johannes Berg
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=20250225182514.GA512422@bhelgaas \
--to=helgaas@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=mukesh.sisodiya@intel.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