From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Peer, Ilan" <ilan.peer@intel.com>,
"anarcat@debian.org" <anarcat@debian.org>
Subject: Re: Microcode SW error since Linux 6.5
Date: Wed, 4 Oct 2023 07:51:02 +0000 [thread overview]
Message-ID: <42e000913e3af714c77fb7a55dd898733e271be0.camel@intel.com> (raw)
In-Reply-To: <5d0904a4-bc0d-42dd-aae8-6b50e5c567ba@leemhuis.info>
Hi,
On Tue, 2023-10-03 at 13:52 +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> [CCing the regressions list]
>
> On 25.09.23 21:03, Johannes Berg wrote:
> > On Mon, 2023-09-25 at 14:39 -0400, Antoine Beaupré wrote:
> > > > Did that patch help?
> > >
> > > I haven't tried, to be honest. It's been years since I compiled a
> > > kernel, so I haven't actually seriously considered it. But I can
> > > definitely put that on my list if it would be useful for you!
> > Heh ok. Well we can also try it I guess. Or reason our way through it,
> > but I'm pretty sure something like that should be done here.
> >
> > > > Yes, you can ... but I mean, we still do want to consider this a bug, I
> > > > think, since we explicitly built the thing to load the older firmware.
> > > > It just gets _far_ less testing.
> > >
> > > Got it, happy to play guinea pig a little further if that's useful.
> > Well you might want to go for the extra stability instead :-) I'm kind
> > of thinking along the lines of "if you can download the next wifi
> > firmware with the current one, that's probably good enough". :)
>
> Well, that's not how Linus wants things to be, as due to this "no
> regression" rule things should continue to work if people update the
> kernel without updating linux-firmware (as also explained in
> Documentation/driver-api/firmware/firmware-usage-guidelines.rst).
>
> That's what I though when I saw that message initially, but I thought:
> well, not worth a comment, the reporter apparently doesn't mind that
> much. But since then I saw more and more reports that looked related to
> my untrained eyes (and thus might not be related at all!).
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217894
> https://bugzilla.kernel.org/show_bug.cgi?id=217894#c6 (same ticket)
> https://bugzilla.kernel.org/show_bug.cgi?id=217963
> https://lore.kernel.org/all/f6448719-14e2-4962-ac3d-1be3c19156ed@dolce-energy.com/
>
> Gregory, Johannes, is there something wrong here with 6.5.y? If yes: is
> anything already been done to improve the state of things?
>
> 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.
The patch in [1] should solve the issue. The problem was that wrong version
of Firmware API was used for some older versions.
[1] https://patchwork.kernel.org/project/linux-wireless/patch/20230926165546.086e635fbbe6.Ia660f35ca0b1079f2c2ea92fd8d14d8101a89d03@changeid/
next prev parent reply other threads:[~2023-10-04 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 17:24 Microcode SW error since Linux 6.5 Antoine Beaupré
2023-09-21 19:10 ` Greenman, Gregory
2023-09-21 19:29 ` Johannes Berg
2023-09-25 2:43 ` Antoine Beaupré
2023-09-25 6:03 ` Johannes Berg
2023-09-25 18:39 ` Antoine Beaupré
2023-09-25 19:03 ` Johannes Berg
2023-10-03 11:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04 7:51 ` Greenman, Gregory [this message]
2023-10-04 8:35 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04 13:12 ` Kalle Valo
2023-10-04 15:34 ` 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=42e000913e3af714c77fb7a55dd898733e271be0.camel@intel.com \
--to=gregory.greenman@intel.com \
--cc=anarcat@debian.org \
--cc=ilan.peer@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox