From: Johannes Berg <johannes@sipsolutions.net>
To: "Antoine Beaupré" <anarcat@debian.org>, linux-wireless@vger.kernel.org
Cc: Gregory Greenman <gregory.greenman@intel.com>, ilan.peer@intel.com
Subject: Re: Microcode SW error since Linux 6.5
Date: Mon, 25 Sep 2023 21:03:48 +0200 [thread overview]
Message-ID: <7bd483fd0d004aed37931561a7faa2e176ca3fac.camel@sipsolutions.net> (raw)
In-Reply-To: <8734z29jx7.fsf@angela.anarc.at>
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". :)
johannes
next prev parent reply other threads:[~2023-09-25 19:03 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 [this message]
2023-10-03 11:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04 7:51 ` Greenman, Gregory
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=7bd483fd0d004aed37931561a7faa2e176ca3fac.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anarcat@debian.org \
--cc=gregory.greenman@intel.com \
--cc=ilan.peer@intel.com \
--cc=linux-wireless@vger.kernel.org \
/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