From: Greg KH <gregkh@linuxfoundation.org>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Gong, Richard" <Richard.Gong@amd.com>
Subject: Re: Allow playing dead in C3 for 5.15.y
Date: Thu, 14 Apr 2022 15:12:50 +0200 [thread overview]
Message-ID: <Ylgd0ntrAM/y4eLk@kroah.com> (raw)
In-Reply-To: <BL1PR12MB5157EDD7F142FB7F214E179CE2EF9@BL1PR12MB5157.namprd12.prod.outlook.com>
On Thu, Apr 14, 2022 at 12:59:09PM +0000, Limonciello, Mario wrote:
> [AMD Official Use Only]
>
>
>
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Thursday, April 14, 2022 05:57
> > To: Limonciello, Mario <Mario.Limonciello@amd.com>
> > Cc: stable@vger.kernel.org; Gong, Richard <Richard.Gong@amd.com>
> > Subject: Re: Allow playing dead in C3 for 5.15.y
> >
> > On Tue, Apr 12, 2022 at 10:15:37PM +0000, Limonciello, Mario wrote:
> > > [Public]
> > >
> > > Hi,
> > >
> > > A change went into 5.17 to allow CPUs to play dead in the C3 state which
> > fixed freezes on s2idle entry if a CPU is offlined by a user.
> > > This has had some time to bake now, and a regression was identified on an
> > ancient machine that is now fixed.
> > >
> > > Can you please backport these commits to 5.15.y to fix that problem and
> > avoid the regression?
> > > commit d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 ("ACPI: processor
> > idle: Allow playing dead in C3 state")
> >
> > Now queued up.
> >
> > > commit 0f00b1b00a44bf3b5e905dabfde2d51c490678ad ("ACPI: processor:
> > idle: fix lockup regression on 32-bit ThinkPad T40").
>
> My apologies; I must have had two references in my tree. The correct hash is
> bfe55a1f7fd6bfede16078bf04c6250fbca11588
That worked, thanks.
prev parent reply other threads:[~2022-04-14 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 22:15 Allow playing dead in C3 for 5.15.y Limonciello, Mario
2022-04-14 10:57 ` Greg KH
2022-04-14 12:59 ` Limonciello, Mario
2022-04-14 13:12 ` Greg KH [this message]
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=Ylgd0ntrAM/y4eLk@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Mario.Limonciello@amd.com \
--cc=Richard.Gong@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox