lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hk1qaui3w.wl-tiwai@suse.de>
Date:   Thu, 05 Jul 2018 11:50:11 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Thomas Hänig <haenig@...ifan.de>,
        Linux PM <linux-pm@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION 4.17] Spurious wakeup / reboot with power button

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@...e.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ