From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux PM <linux-pm@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: Linux 5.6-rc2
Date: Thu, 20 Feb 2020 23:41:22 +0100 [thread overview]
Message-ID: <10791544.HYfhKnFLvn@kreacher> (raw)
In-Reply-To: <158197497594.2449.9692451182044632969@skylake-alporthouse-com>
On Monday, February 17, 2020 10:29:35 PM CET Chris Wilson wrote:
> Quoting Linus Torvalds (2020-02-17 21:20:27)
> > On Mon, Feb 17, 2020 at 8:22 AM Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > >
> > > Quoting Linus Torvalds (2020-02-16 21:32:32)
> > > > Rafael J. Wysocki (4):
> > > > ACPI: EC: Fix flushing of pending work
> > > > ACPI: PM: s2idle: Avoid possible race related to the EC GPE
> > > > ACPICA: Introduce acpi_any_gpe_status_set()
> > > > ACPI: PM: s2idle: Prevent spurious SCIs from waking up the system
> > >
> > > Our S0 testing broke on all platforms, so we've reverted
> > > e3728b50cd9b ("ACPI: PM: s2idle: Avoid possible race related to the EC GPE")
> > > fdde0ff8590b ("ACPI: PM: s2idle: Prevent spurious SCIs from waking up the system")
> > >
> > > There wasn't much in the logs, for example,
> > > https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5445/fi-kbl-7500u/igt@gem_exec_suspend@basic-s0.html
> >
> > So the machine suspends, but never comes back?
> >
> > Do you need to revert both for it to work for you? Or is the revert of
> > fdde0ff8590b just to avoid the conflict?
>
> fdde0ff85 was just to avoid conflicts.
>
> > I'm assuming you bisected this, and the bisect indicated e3728b50cd9b,
> > and then to revert it you reverted the other commit too..
>
> Lucky guess based on diff rc1..rc2. Bisect was going to be painful, but
> could be done if this is not enough clue for Rafael.
Sorry for the delayed response, was away.
I'm guessing that you are using rtcwake for wakeup, in which case reverting
fdde0ff85 alone should unbreak it.
Can you please double check that?
next prev parent reply other threads:[~2020-02-20 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 21:32 Linux 5.6-rc2 Linus Torvalds
2020-02-17 2:08 ` Dave Jones
2020-02-17 2:24 ` Linus Torvalds
2020-02-17 3:02 ` Josef Bacik
2020-02-17 5:08 ` Linus Torvalds
2020-02-17 12:30 ` David Sterba
2020-02-17 16:45 ` Dave Jones
2020-02-17 16:04 ` Filipe Manana
2020-02-17 16:21 ` Chris Wilson
2020-02-17 21:20 ` Linus Torvalds
2020-02-17 21:29 ` Chris Wilson
2020-02-20 22:41 ` Rafael J. Wysocki [this message]
2020-02-21 0:46 ` Rafael J. Wysocki
2020-02-21 9:19 ` Chris Wilson
[not found] ` <CAJZ5v0h07em8y5bXcnUTBcjie8pCttADK9QX9W_cB0WQRcDfGQ@mail.gmail.com>
2020-02-21 18:02 ` Linus Torvalds
2020-02-23 23:57 ` Rafael J. Wysocki
2020-02-17 18:42 ` sinisa
2020-02-17 20:17 ` Dominik Brodowski
2020-02-21 1:38 ` Dave Airlie
2020-02-21 2:23 ` [Intel-gfx] " Souza, Jose
2020-02-24 18:24 ` Siniša Bandin
2020-03-02 16:39 ` Siniša Bandin
2020-03-02 17:04 ` Jani Nikula
2020-03-03 7:08 ` Sinisa
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=10791544.HYfhKnFLvn@kreacher \
--to=rjw@rjwysocki.net \
--cc=chris@chris-wilson.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).