From: Takashi Iwai <tiwai@suse.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Thomas Hänig" <haenig@cosifan.de>,
"Linux PM" <linux-pm@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION 4.17] Spurious wakeup / reboot with power button
Date: Thu, 05 Jul 2018 11:50:11 +0200 [thread overview]
Message-ID: <s5hk1qaui3w.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAJZ5v0guCPET3gM-G_NAM-BjER2D3yW2i_CwR-5sHyNzCQ6R+Q@mail.gmail.com>
On Thu, 05 Jul 2018 11:34:59 +0200,
Rafael J. Wysocki wrote:
>
> Hi,
>
> On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > Hi,
> >
> > we've got a regression report since 4.17 about the behavior of
> > power-off with the power button. When a machine is powered off with
> > the power button on desktop, it reboots after a few seconds instead of
> > power down.
> >
> > The manual power down via "systemctl poweroff" works fine, so it's
> > possibly some spurious wakeup by the power button action, and some
> > ACPI-related change is suspected.
> > The regression still remains in 4.18-rc3.
>
> There are only a few ACPI commits directly related to power management
> between 4.16 and 4.17 and none of them looks particularly suspicious.
OK, interesting.
> It looks like the power button state may not be cleared sufficiently
> after it's been pressed which is now visible for some reason.
Hmm, where can such a state remain? Since it happens after the
machine turned off, some (ACPI) wakeup bits?
> How does the button poweroff work, exactly? I guess the event is
> collected by a user space demon which then triggers power of via sysfs
> or similar?
Usually X desktop environment receives an input event from the ACPI
power button input device, and deals the event accordingly depending
on the setup. The power-down behavior itself should be equivalent
with "systemctl poweroff" or such.
thanks,
Takashi
next prev parent reply other threads:[~2018-07-05 9:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 7:05 [REGRESSION 4.17] Spurious wakeup / reboot with power button Takashi Iwai
2018-07-05 9:34 ` Rafael J. Wysocki
2018-07-05 9:50 ` Takashi Iwai [this message]
2018-07-05 9:58 ` Thomas Hänig
2018-07-05 10:00 ` Takashi Iwai
2018-07-05 10:16 ` Rafael J. Wysocki
2018-07-05 10:41 ` Rafael J. Wysocki
2018-07-05 12:12 ` Takashi Iwai
2018-07-05 12:19 ` Thomas Hänig
2018-07-05 14:00 ` Thomas Hänig
2018-07-05 15:09 ` Takashi Iwai
2018-07-05 15:10 ` Rafael J. Wysocki
2018-07-05 16:02 ` Rafael J. Wysocki
2018-07-05 16:56 ` Takashi Iwai
2018-07-05 18:18 ` Thomas Hänig
2018-07-06 5:18 ` Thomas Hänig
2018-07-06 6:55 ` Takashi Iwai
2018-07-06 9:40 ` Rafael J. Wysocki
2018-07-06 9:53 ` Takashi Iwai
2018-07-06 11:12 ` Thomas Hänig
2018-07-06 11:21 ` Rafael J. Wysocki
2018-07-06 12:13 ` Rafael J. Wysocki
2018-07-06 12:27 ` Takashi Iwai
2018-07-06 12:53 ` Thomas Hänig
2018-07-06 17:57 ` Thomas Hänig
2018-07-08 8:18 ` Rafael J. Wysocki
2018-07-06 12:49 ` Thomas Hänig
2018-07-08 9:10 ` [PATCH] ACPICA: Clear status of all events when entering S5 Rafael J. Wysocki
2018-07-16 17:59 ` Schmauss, Erik
2018-07-17 7:23 ` 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=s5hk1qaui3w.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=haenig@cosifan.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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).