From: Johannes Berg <johannes@sipsolutions.net>
To: Bjorn Helgaas <helgaas@kernel.org>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
emmanuel.grumbach@intel.com
Cc: "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: Wed, 05 Mar 2025 13:56:19 +0100 [thread overview]
Message-ID: <db6e127f5f7cfaf76bbf4438ae8962993f4aba03.camel@sipsolutions.net> (raw)
In-Reply-To: <20250303222700.GA202089@bhelgaas>
[removing folks no longer involved]
Hi,
So ... it's complicated, but I think it's a bug.
> 4886460c4d15 ("iwlwifi: Fix IWL_SUBDEVICE_NO_160 macro to use the
> correct bit.") updated IWL_SUBDEVICE_NO_160() to identify devices that
> should not support 160MHz:
>
> -#define IWL_SUBDEVICE_NO_160(subdevice) ((u16)((subdevice) & 0x0100) >> 9)
> +#define IWL_SUBDEVICE_NO_160(subdevice) ((u16)((subdevice) & 0x0200) >> 9)
I'm not even entirely sure this logic is correct; however, it doesn't
really matter.
> The submitter's device has Subdevice ID 0x1652. Prior to
> 4886460c4d15, that did not match IWL_SUBDEVICE_NO_160(), but
> afterwards it does:
>
> 0000:00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi WiFi [8086:51f0] (rev 01)
> Subsystem: Rivet Networks Dual Band Wi-Fi 6(802.11ax) Killer AX1650i 160MHz 2x2 [Cyclone Peak] [1a56:1652]
According to our internal information (SKUMAP-362, for the Intel folks
who know what that means), this name is correct, it should be 160 Mhz.
> But apparently it wasn't until 84ec2d2e960f ("wifi: iwlwifi: disable
> 160 MHz based on subsystem device ID"), that 160MHz support actually
> got disabled for devices that match IWL_SUBDEVICE_NO_160():
I've also found information elsewhere (WREQ-269994) that the whole
IWL_SUBDEVICE_NO_160 (now actually a bit different to take no-320 into
account on newer hardware) is *not* applicable to "Killer" branded
devices at all.
So I think it's a bug, but I'm not sure right now *how* we can fix it.
It looks like our matching must skip the bandwidth restriction thing for
Killer devices.
johannes
prev parent reply other threads:[~2025-03-05 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 9:12 Linux regression tracking (Thorsten Leemhuis)
2024-08-08 6:43 ` Linux regression tracking (Thorsten Leemhuis)
2025-02-25 18:25 ` Bjorn Helgaas
2025-03-03 22:27 ` Bjorn Helgaas
2025-03-05 12:56 ` Johannes Berg [this message]
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=db6e127f5f7cfaf76bbf4438ae8962993f4aba03.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@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
all inboxes | Powered by JetHome®