From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Jason Self <jason@bluehome.net>, Stefan Agner <stefan@agner.ch>,
Greg KH <gregkh@linuxfoundation.org>,
Johannes Berg <johannes.berg@intel.com>,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Regression/boot failure on 5.16.3
Date: Tue, 8 Feb 2022 19:22:25 +0100 [thread overview]
Message-ID: <df18cc2e-fa46-b088-85c6-959d8b6ea4ea@leemhuis.info> (raw)
In-Reply-To: <20220208100529.41d1b4d7@valencia>
On 08.02.22 19:05, Jason Self wrote:
> On Tue, 08 Feb 2022 09:50:59 +0100
> Stefan Agner <stefan@agner.ch> wrote:
>
>> On 2022-02-04 01:19, Jason Self wrote:
>> [...]
>>
>> I have several reports of Intel NUC 10th/11th gen not booting/crashing
>> during boot after updating to 5.10.96 (from 5.10.91). At least one
>> stack trace shows iwl_dealloc_ucode in the call path. The below
>> commit is part of 5.10.96 So this regression seems to not only affect
>> 5.16 series.
>>
>> Link:
>> https://github.com/home-assistant/operating-system/issues/1739#issuecomment-1032013069
>
> Yes, it does appear to affect multiple versions; at least 5.17-rc2,
> 5.16, 5.15, and as you say 5.10.
>
> I can confirm that this patch addresses it on 5.16:
> https://lore.kernel.org/stable/YgJSEEmRDKKG+3lT@mail-itl/T/#t
Thx for pointing to the thread!
#regzbot monitor: https://lore.kernel.org/stable/YgJSEEmRDKKG+3lT@mail-itl/
> It appears desirable to apply the patch to all of the stable versions
> that need it, after it's gone into Linus's tree to also address the
> matter with the upcoming 5.17 series.
FWIW, the patch is marked for backporting already, it just needs to get
merged to mainline first.
Ciao, Thorsten
prev parent reply other threads:[~2022-02-08 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 0:19 Regression/boot failure on 5.16.3 Jason Self
2022-02-04 7:00 ` Greg KH
2022-02-04 8:48 ` Thorsten Leemhuis
2022-02-08 8:50 ` Stefan Agner
2022-02-08 18:05 ` Jason Self
2022-02-08 18:22 ` Thorsten Leemhuis [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=df18cc2e-fa46-b088-85c6-959d8b6ea4ea@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=jason@bluehome.net \
--cc=johannes.berg@intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=stefan@agner.ch \
/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;
as well as URLs for NNTP newsgroup(s).