From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>,
"Kenneth R. Crudup" <kenny@panix.com>
Cc: Linux PM <linux-pm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] ACPI: PM: s2idle: Fix possible suspend lock-up
Date: Thu, 28 Nov 2019 23:42:09 +0100 [thread overview]
Message-ID: <2787005.CsmIKtZlk9@kreacher> (raw)
Hi All,
The first patch in this series is a fix for a suspend-to-idle issues introduced
in 5.4 (see its changelog for details).
The second one is more of an optimization, although some systems may need it
too (depending on how fragile their platform firmware is).
Kenneth,
This series is roughly equivalent to the patch at
https://lore.kernel.org/linux-pm/CAJZ5v0h1Ro75++4xuCznkx6GNYd+G5NpMGP96z1jdh=dm9uZbw@mail.gmail.com/T/#m11ca9a14efe4e5193bbda69767595a5fb7bd5479
The main difference is that it flushes system_wq before ec_query_wq, but that
should not really matter if the issue you saw in 5.4 is the one described
in the changelog of patch [1/2].
Please test this series and let me know if it works for you too.
In case it does work, it would be good to know if patch [1/2] is sufficient to
fix the suspend problem at least with ec_no_wakeup == 0 (it may not be
sufficient with ec_no_wakeup == 1).
Thanks!
next reply other threads:[~2019-11-28 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 22:42 Rafael J. Wysocki [this message]
2019-11-28 22:47 ` [PATCH 1/2] ACPI: EC: Rework flushing of pending work Rafael J. Wysocki
2019-11-28 22:50 ` [PATCH 2/2] ACPI: PM: s2idle: Rework ACPI events synchronization Rafael J. Wysocki
2019-11-29 20:35 ` [PATCH 0/2] ACPI: PM: s2idle: Fix possible suspend lock-up Kenneth R. Crudup
2019-12-01 19:54 ` 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=2787005.CsmIKtZlk9@kreacher \
--to=rjw@rjwysocki.net \
--cc=kenny@panix.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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