Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp429918imm; Thu, 5 Jul 2018 02:51:08 -0700 (PDT) X-Google-Smtp-Source: AAOMgpe9aQNjC2MuBsDjtwHFtLHsd/MNy3kmboYHhwjMhD7A0McCLP5ytBNilSbtw0Npd6gVvLlT X-Received: by 2002:a17:902:2c83:: with SMTP id n3-v6mr5414903plb.211.1530784268619; Thu, 05 Jul 2018 02:51:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530784268; cv=none; d=google.com; s=arc-20160816; b=0v/k6bKCjgY2FTL0+VUdOPrHI8N8Wl62cYVhQ7Zto4V4h5GIGuFtexInsCJ4PgUbPy LKff6YKgC6o3aUteQY95OJ3r+Iun4YorfhfiLr759h7I5jnwhNTraeFoQE9kHBd6Dokl oAh+dtZf/NK9uAlOAT6r9zDaNd66jPPeH5q1jdtZtrWk/82vdbLUKpuwrJXRa2FLUFZ9 WaIQBSgCuasvL/k+6G7JndhW6wScjFqKIY3AL/D4J/NXrhwp8IobhT+ST9U2l2Ivk+M+ rCSlhnD225GSpm06EMwf1a02PlD00ozHjza2qCKlgDz7luR3Wum3ngqRRNyONG3nMQme PT0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date :arc-authentication-results; bh=295xt3PRAlGmaPFVaqrLdLc5Mhin9+z7xSZFtOetyWw=; b=CpC5CyrGKro3/+Ot/z6XLmaba2aVtr7Qx4iQ8wI5N3CBVa6elfKEk5BajoKZu0WTyH mtHvtrC+i3eL62iPA3rbS1DXjOLZvaYbYng0KPYzCFWyR9DLLIkZs6U1pABi3CCioJc3 T6RmxA04YDd5xYGZlxZf7wYr8VDcM7OnKq1HdQXiUe9DVsopiB+EmWa9TGBtkNhBJixP eupsPY1azNqKJCTK/fuyjOG8RT9TbTmAsv0mAaoAZrAhzvbnqffB0NuhJxgiDoq1e/z2 viTDfWZhFToYXT74aiNbnjBloz+hVHwvovtBQufU11irQYUfruldWV9i6zOh1gN7O3iU 4S4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1-v6si5445821plj.411.2018.07.05.02.50.54; Thu, 05 Jul 2018 02:51:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753403AbeGEJuP (ORCPT + 99 others); Thu, 5 Jul 2018 05:50:15 -0400 Received: from mx2.suse.de ([195.135.220.15]:47794 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753070AbeGEJuO (ORCPT ); Thu, 5 Jul 2018 05:50:14 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 18F1CACCF; Thu, 5 Jul 2018 09:50:13 +0000 (UTC) Date: Thu, 05 Jul 2018 11:50:11 +0200 Message-ID: From: Takashi Iwai To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , Thomas =?UTF-8?B?SMOkbmln?= , Linux PM , Linux Kernel Mailing List Subject: Re: [REGRESSION 4.17] Spurious wakeup / reboot with power button In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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