Re: [PATCH 7.2 000/243] 7.2.13-rc2 review

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Sat, Oct 24, 2026 at 11:08:02AM -0700, Barry K. Nathan wrote:
> 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.

Ok, let me go drop all of these patches and push out a -rc3, thanks for
testing and letting me know!

greg k-h