From: "Barry K. Nathan" <barryn@pobox.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 7.2 000/243] 7.2.13-rc2 review
Date: Sat, 24 Oct 2026 11:08:02 -0700 [thread overview]
Message-ID: <c2227d20-c533-47ad-8446-aa0838f7c0be@pobox.com> (raw)
In-Reply-To: <a65e25c3-b1ea-4b8b-bf3b-c5de0d069b22@pobox.com>
On 10/24/26 7:32 AM, Barry K. Nathan wrote:
> On 10/23/26 11:59 PM, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 7.2.13 release.
>> There are 243 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Mon, 26 Oct 2026 06:46:54 +0000.
>> Anything received after that time might be too late.
>>
>> The whole patch series can be found in one patch at:
>> https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.2.13-rc2.gz
>> or in the git tree and branch at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-7.2.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> With 7.2.13-rc2, each time I go through a suspend/wake cycle on my Lenovo
> ThinkPad T14 Gen 1, the following line appears in dmesg:
>
> (NULL device *): Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
>
> This is new and appears to be a regression, and it is 100% reproducible.
> It does not occur with 7.3.0, 7.2.12, or 6.18.59-rc1. I will start
> bisecting it shortly after I send this email.
>
> In case it's relevant, my ThinkPad T14 Gen 1 has an Intel Core i5-10310U
> CPU (Comet Lake-U), and it's running an up-to-date Debian trixie.
It bisected down to these two patches:
fs-add-umh-argument-to-struct-kernel_clone_args.patch
fs-stop-sharing-fs_struct-between-init_task-and-pid-1.patch
That is, with all of the patches prior to fs-add-umh... the bug does not
reproduce. With fs-add-umh... the 7.2.13-rc1 boot problem happens, and
adding fs-stop-sharing... fixes the boot problem, but now I have the
new message when suspending.
dmesg context before and after the new message (should've included this
in my previous email, sorry):
[ 55.793416] PM: suspend entry (deep)
[ 55.825734] Filesystems sync: 0.032 seconds
[ 55.825812] (NULL device *): Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
[ 55.826364] Freezing user space processes
[ 55.827740] Freezing user space processes completed (elapsed 0.001 seconds)
[ 55.827744] OOM killer disabled.
[ 55.827745] Freezing remaining freezable tasks
[ 55.828885] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 55.828941] printk: Suspending console(s) (use no_console_suspend to debug)
Except for the new "(NULL device [...] error -2" message, all of the
others are the messages that normally appear when suspending.
--
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2026-10-24 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 6:59 Greg Kroah-Hartman
2026-10-24 10:58 ` Brett A C Sheffield
2026-10-24 14:10 ` Miguel Ojeda
2026-10-24 14:32 ` Barry K. Nathan
2026-10-24 18:08 ` Barry K. Nathan [this message]
2026-10-24 16:01 ` Markus Reichelt
2026-10-24 20:16 ` Peter Schneider
2026-10-24 20:30 ` Justin Forbes
2026-10-24 21:10 ` SJ Park
2026-10-24 21:17 ` Pavel Machek
2026-10-25 0:30 ` Ron Economos
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=c2227d20-c533-47ad-8446-aa0838f7c0be@pobox.com \
--to=barryn@pobox.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®