linux-kernel - Re: [regression] 6.8.1 and 6.7.12: fails to hibernate with pm_runtime_force

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 5 Apr 2024 15:34:30 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Martin Steigerwald <martin@...htvoll.de>
Cc: linux-pm@...r.kernel.org, regressions@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [regression] 6.8.1 and 6.7.12: fails to hibernate with
 pm_runtime_force_suspend+0x0/0x120 returns -16

On Fri, Apr 05, 2024 at 02:11:11PM +0200, Martin Steigerwald wrote:
> Martin Steigerwald - 05.04.24, 13:54:34 CEST:
> > > Not doing it today or probably the weekend, but now I have some
> > > actionable git bisect plan without bisecting between major kernel
> > > releases which as I have been told between 6.7 an 6.8-rc1 can lead to
> > > non working modeset graphics on AMD Ryzen in between.
> > > 
> > > It seems now I only need to git bisect between 6.7.11 and 6.7.12 to
> > > find the patch that breaks hibernation on 6.8.1 as well. However
> > > first I will briefly check whether 6.8.4 hibernates okay.
> > 
> > 6.8.4 is still affected and fails hibernation with the same error
> > message.
> 
> Both kernels also fail to reboot the machine. Runit says:
> 
> - runit: system reboot
> 
> And then nothing anymore.
> 
> It is not just hibernation.
> 
> I think ThinkPad T14 AMD Gen 1 or similar systems with Linux are not that 
> rare. I am surprised this is not hitting more people. Well maybe it does 
> and no one reported it here.
> 
> Well let's see what happens when 6.7.12 hits distribution kernels.
> 
> Anyway, I have an actionable git bisect between 6.7.11 and 6.7.12, just 
> not today. Maybe beginning of next week.

6.7.y is end-of-life, I wouldn't worry too much about it, there's
nothing we can do about it anymore, sorry.

greg k-h