public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-pm@vger.kernel.org, regressions@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: [regression] 6.8.1: fails to hibernate with pm_runtime_force_suspend+0x0/0x120 returns -16
Date: Fri, 05 Apr 2024 13:49:00 +0200	[thread overview]
Message-ID: <6034738.lOV4Wx5bFT@lichtvoll.de> (raw)
In-Reply-To: <be5a7213-78b3-4917-b95b-ec31cd2350e4@leemhuis.info>

Linux regression tracking (Thorsten Leemhuis) - 19.03.24, 09:40:06 CEST:
> On 16.03.24 17:12, Martin Steigerwald wrote:
> > Martin Steigerwald - 16.03.24, 17:02:44 CET:
> >> ThinkPad T14 AMD Gen 1 fails to hibernate with self-compiled 6.8.1.
> >> Hibernation works correctly with self-compiled 6.7.9.
> > 
> > Apparently 6.8.1 does not even reboot correctly anymore. runit on
> > Devuan. It says it is doing the system reboot but then nothing
> > happens.
> > 
> > As for hibernation the kernel cancels the attempt and returns back to
> > user space desktop session.
> > 
> >> Trying to use "no_console_suspend" to debug next. Will not do bisect
> >> between major kernel releases on a production machine.
> 
> FWIW, without a bisection I guess no developer will take a closer look
> (but I might be wrong and you lucky here!), as any change in those
> hundreds of drivers used on that machine can possibly lead to problems
> like yours. So without a bisection we are likely stuck here, unless
> someone else runs into the same problem and bisects or fixes it. Sorry,
> but that's just how it is.

The plot thickens, now 6.7.12 as compared to 6.7.11 which failed hibernation
with busy work queues¹ and 6.7.9 + bcachefs downgrade fixes fails
hibernation with the same error message than 6.8.1:

[   74.330285] PM: hibernation: hibernation entry
[   74.617009] Filesystems sync: 0.097 seconds
[   74.617309] Freezing user space processes
[   74.620021] Freezing user space processes completed (elapsed 0.002 seconds)
[   74.620048] OOM killer disabled.
[   74.620250] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
[   74.620253] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
[   74.620256] PM: hibernation: Marking nosave pages: [mem 0x09c00000-0x09d00fff]
[   74.620261] PM: hibernation: Marking nosave pages: [mem 0x09f00000-0x09f0ffff]
[   74.620263] PM: hibernation: Marking nosave pages: [mem 0xa22b7000-0xa22b7fff]
[   74.620264] PM: hibernation: Marking nosave pages: [mem 0xa22c4000-0xa22c5fff]
[   74.620266] PM: hibernation: Marking nosave pages: [mem 0xa22d3000-0xa22d4fff]
[   74.620267] PM: hibernation: Marking nosave pages: [mem 0xa22e5000-0xa22e5fff]
[   74.620269] PM: hibernation: Marking nosave pages: [mem 0xb9533000-0xb95c3fff]
[   74.620272] PM: hibernation: Marking nosave pages: [mem 0xbd9de000-0xcc3fdfff]
[   74.620752] PM: hibernation: Marking nosave pages: [mem 0xce000000-0xffffffff]
[   74.622717] PM: hibernation: Basic memory bitmaps created
[   74.629269] PM: hibernation: Preallocating image memory
[   76.658495] PM: hibernation: Allocated 2042025 pages for snapshot
[   76.658875] PM: hibernation: Allocated 8168100 kbytes in 2.02 seconds (4043.61 MB/s)
[   76.658901] Freezing remaining freezable tasks
[   76.660457] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[   76.666115] port 0000:02:00.1:0.0: PM: dpm_run_callback(): pm_runtime_force_suspend+0x0/0x120 returns -16
[   76.666255] port 0000:02:00.1:0.0: PM: failed to freeze: error -16
[   78.616495] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4694]
[   78.654349] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..]
[   79.106531] PM: hibernation: Basic memory bitmaps freed
[   79.106855] OOM killer enabled.
[   79.106873] Restarting tasks ... done.
[   79.111514] PM: hibernation: hibernation exit

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.

[1] * 6.7.11: Fails to hibernate - work queues still busy
@ 2024-04-02 19:29 Martin Steigerwald

https://lore.kernel.org/regressions/2ad93b57-8fdc-476e-83b7-2c0af1cfd41d@leemhuis.info/T/#t

Best,
-- 
Martin



  parent reply	other threads:[~2024-04-05 11:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 16:02 [regression] 6.8.1: fails to hibernate with pm_runtime_force_suspend+0x0/0x120 returns -16 Martin Steigerwald
2024-03-16 16:12 ` Martin Steigerwald
2024-03-19  8:40   ` Linux regression tracking (Thorsten Leemhuis)
2024-04-02 19:42     ` Martin Steigerwald
2024-04-03  4:49       ` Linux regression tracking (Thorsten Leemhuis)
2024-04-05 11:49     ` Martin Steigerwald [this message]
2024-04-05 11:54       ` Martin Steigerwald
2024-04-05 12:11         ` [regression] 6.8.1 and 6.7.12: " Martin Steigerwald
2024-04-05 13:34           ` Greg KH
2024-04-05 14:38             ` Martin Steigerwald
2024-04-05 12:18         ` [regression] 6.8.1: " Martin Steigerwald

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=6034738.lOV4Wx5bFT@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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