All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: Hans de Goede <hdegoede@redhat.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	Stable <stable@vger.kernel.org>,
	Justin Forbes <jmforbes@linuxtx.org>,
	Mark Pearson <markpearson@lenovo.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: RE: Many reports of laptops getting hot while suspended with kernels >= 5.16.10 || >= 5.17-rc1
Date: Wed, 16 Mar 2022 16:14:19 +0000	[thread overview]
Message-ID: <BL1PR12MB5157D1E7EBB32F66C284DE0FE2119@BL1PR12MB5157.namprd12.prod.outlook.com> (raw)
In-Reply-To: <b559b406-006e-05e6-6378-4665ff721666@redhat.com>

[Public]


> > Hans,
> >
> > Do you think you could get one of the folks who reported this regression to
> do
> > a bisect to see which one "fixed" it?
> 
> We already know which commit is causing the regression. As Rafael already
> said the question is why things are not broken in 5.17 and that is not
> a straight forward bisect. So figuring this out is going to be a lot
> of work and I'm not sure of that it is worth it. I certainly don't
> have time to help users with debugging this.
> 
> > If we get lucky we can come down to
> > some smaller hunks of code that can come back to stable instead of
> reverting.
> 
> 5.17 is almost done and in a couple of weeks Fedora (and Arch and other
> distros tracking the mainline kernel) will move to 5.17 resolving the
> wakeup by keyboard issue not working there.
> 
> 5.16 is not a LTS kernel, so for other distros we would at a minimum
> figure out what needs to be backported to make things work with 5.15
> making the delta / set of possible patches we need even bigger.
> So as already said IMHO this is not worth it, at least assuming that
> nothing bad happens when attempting wakeup by keyboard, iow it
> just does not work and does not put the laptop in some bad state?
> 
> Regards,
> 
> Hans

You're right, no bad state as a result and probably not worth the tradeoff for a bisect effort.
OK, thanks.

  reply	other threads:[~2022-03-16 16:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 13:44 Many reports of laptops getting hot while suspended with kernels >= 5.16.10 || >= 5.17-rc1 Hans de Goede
2022-03-09 13:57 ` Rafael J. Wysocki
2022-03-09 16:31   ` Hans de Goede
2022-03-09 16:34     ` Rafael J. Wysocki
2022-03-09 18:27       ` Rafael J. Wysocki
2022-03-10  9:07         ` Hans de Goede
2022-03-10 10:56           ` Rafael J. Wysocki
2022-03-10 12:22             ` Hans de Goede
2022-03-14 14:37               ` Limonciello, Mario
2022-03-16 13:02                 ` Rafael J. Wysocki
2022-03-16 13:37                   ` Limonciello, Mario
2022-03-16 13:46                     ` Rafael J. Wysocki
2022-03-16 13:50                       ` Limonciello, Mario
2022-03-16 16:00                     ` Hans de Goede
2022-03-16 16:14                       ` Limonciello, Mario [this message]
2022-03-10 10:02 ` Thorsten Leemhuis
2022-03-10 10:58   ` Rafael J. Wysocki

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=BL1PR12MB5157D1E7EBB32F66C284DE0FE2119@BL1PR12MB5157.namprd12.prod.outlook.com \
    --to=mario.limonciello@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=jmforbes@linuxtx.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=markpearson@lenovo.com \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.