From: Martin Steigerwald <martin@lichtvoll.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-pm@vger.kernel.org, regressions@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [regression] 6.8.1 and 6.7.12: fails to hibernate with pm_runtime_force_suspend+0x0/0x120 returns -16
Date: Fri, 05 Apr 2024 16:38:23 +0200 [thread overview]
Message-ID: <2181810.irdbgypaU6@lichtvoll.de> (raw)
In-Reply-To: <2024040512-defective-wreckage-f202@gregkh>
Greg KH - 05.04.24, 15:34:30 CEST:
> > 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.
Ah, I see. Thanks.
Still its a good short cut for bisection. Bisecting between 6.7.11 and
6.7.12 should get much quicker results than bisecting between 6.7 and 6.8
and as its the same error message in 6.8.1/6.8.4 and 6.7.12 it might be
the same (backported) patch causing the issue.
--
Martin
next prev parent reply other threads:[~2024-04-05 14:38 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
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 [this message]
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=2181810.irdbgypaU6@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=gregkh@linuxfoundation.org \
--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