regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: tboot suspend broken on Lenovo T460p #forregzbot
Date: Mon, 26 Sep 2022 15:37:06 +0200	[thread overview]
Message-ID: <ce38e824-2083-fcce-dc6c-2e6d58c132c2@leemhuis.info> (raw)
In-Reply-To: <0b09b35a-64d3-5ba3-dabc-1e36ace1c275@leemhuis.info>

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 29.04.22 14:03, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
> 
> About a week ago a regression was reported to bugzilla.kernel.org that
> seems to be handled there already, nevertheless I'd like to add to the
> tracking to ensure it's not forgotten.
> 
> #regzbot introduced: 453e41085183980087f8a80dada523caf1131c3c
> #regzbot from: Derek Dolney <z23@posteo.net>
> #regzbot title: tboot suspend broken on Lenovo T460p
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215867


#regzbot backburner: fix available, but maintainer didn't pick it up and
developer of the fix is MIA for unkown reason

For details see:
https://lore.kernel.org/lkml/42237005-5a6e-9462-bfdd-f1ba0c725c72@leemhuis.info/

Sigh. That's not how things should be, but happen anyway.

Ciao, Thorsten

> Quote:
> 
>> I am using tboot (v1.10.5) to make use of intel-txt and all was
>> working fine with the Linux kernel 5.10 series. However later in 5.12
>> release candidates, I have  proper booting however suspend is broken.
>> I am using a Lenovo T460p. Usually when suspending on this machine
>> the power button LED will blink 8 times and then it goes into a sleep
>> state. With newer kernels I get power LED and caps lock LED blinking,
>> cpu fan runs fast, and can't get out of that state without hard
>> powerdown.
>>
>> I did a git bisect on and found that commit
>> 453e41085183980087f8a80dada523caf1131c3c is the one that breaks
>> tboot+suspend to ram. It is part of a series of some cpu hotplug
>> commits.
>>
>> Just to be clear: if I build a kernel from the commit just before
>> this one, I can suspend and resume, but if I build with this commit I
>> can not suspend, laptop gets stuck on blinking power LED. Let me also
>> mention that, given the above commit, if I do not use tboot, I can
>> suspend and resume ok. It is only within the tboot boot context that
>> I have suspend&resume problems.
> 
> 
> See the ticket for details, there were a few replies already.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
> 

  reply	other threads:[~2022-09-26 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 12:03 tboot suspend broken on Lenovo T460p Thorsten Leemhuis
2022-09-26 13:37 ` Thorsten Leemhuis [this message]
2022-12-08  7:06   ` tboot suspend broken on Lenovo T460p #forregzbot Thorsten Leemhuis

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=ce38e824-2083-fcce-dc6c-2e6d58c132c2@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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;
as well as URLs for NNTP newsgroup(s).