Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp1588014imm; Fri, 6 Jul 2018 02:54:53 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfR1OskIGMfmIj3iBXnOqNcUSRPH6nwe0eRGf3FjZoNfk52J+0Svh9+fjbcCqZUPR/RgP68 X-Received: by 2002:a63:6cc8:: with SMTP id h191-v6mr8804679pgc.359.1530870893366; Fri, 06 Jul 2018 02:54:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530870893; cv=none; d=google.com; s=arc-20160816; b=uX2EH1e68UERDHI3925zrO6XclE5e4laoz44zTh+wKKlmA400VrevUsmbnKE1QCQ0G tgEx+E784Pwi87bFsqTCDEIDOLO2dnFeDHskWuBJ5oPJ43OSKcyPrykR42tRXew/CF33 6MAg5RTCL/Y3548jkSPxhx6JKLvH1imsRDnDq0VUe5eADl7qArrCid8NHFU2a7DQNhdB YmqDr9GK0YOr5KheUFRu5M4P/jVpmFXew7k8uO9IZnUniMF61HsLrMvMLVCl0qa8zaEt DVAPVncJIsxf+8xCFy/fEDOMbqH8UrXkmRsl/45P8RtP1wC4o9EblMTgeSLZtEiHV+9O 4KhQ== 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=pYNZmiF+GvVaur75YyrsuO74uFjPG8uGHgRxJQt42vo=; b=ZUgC6SYv2AmNcdr/kCWgFnrqk1/t1GYXiDTFTHGEouyMNo+2MJeyV00tJ9O1G5QqWI aljCCL3u2heDPrZ27tMJdsxkgA2oHo9Hcta7pMLTIfb7E5zzwt21HLZl8mltRVrEZ2ZX o+JUS2nsQb3XUvbJRWJNfKtBBWA7B2wV2GxA3saZnZX6x8tnofXqMERe59Be6iSRctfm eWEvh34N7NLeFNgQ99zwUJbW6YgDc9el/Iv72AZygzFTdmWk7gTeqIPtSrhOX8XdvOZR d1uu1jFyPx87XuSsrUezkAYnr1yGIctDgxpXZTE1TtajB2K/Afl3a4EXfJ+8b2uKYSNs O9mg== 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 82-v6si5028139pfo.229.2018.07.06.02.54.37; Fri, 06 Jul 2018 02:54:53 -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 S1753732AbeGFJx6 (ORCPT + 99 others); Fri, 6 Jul 2018 05:53:58 -0400 Received: from mx2.suse.de ([195.135.220.15]:49870 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753367AbeGFJx4 (ORCPT ); Fri, 6 Jul 2018 05:53:56 -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 CEDB4AD04; Fri, 6 Jul 2018 09:53:54 +0000 (UTC) Date: Fri, 06 Jul 2018 11:53:53 +0200 Message-ID: From: Takashi Iwai To: "Rafael J. Wysocki" Cc: Thomas H4nig , Erik Schmauss , Linux PM , Linux Kernel Mailing List , Linux ACPI Subject: Re: [REGRESSION 4.17] Spurious wakeup / reboot with power button In-Reply-To: <10224352.M7fh6vac6O@aspire.rjw.lan> References: <5cce6fa6-c089-7a6b-aaef-bdd04a3761c6@cosifan.de> <10224352.M7fh6vac6O@aspire.rjw.lan> 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 Fri, 06 Jul 2018 11:40:43 +0200, Rafael J. Wysocki wrote: > > On Friday, July 6, 2018 8:55:18 AM CEST Takashi Iwai wrote: > > On Fri, 06 Jul 2018 07:18:36 +0200, > > Thomas H4nig wrote: > > > > > > > > > > > > Am 05.07.2018 um 18:56 schrieb Takashi Iwai: > > > > On Thu, 05 Jul 2018 18:02:11 +0200, > > > > Rafael J. Wysocki wrote: > > > >> > > > >> [The Lv's address is not valid any more, so drop it from the CC] > > > >> > > > >> On Thursday, July 5, 2018 5:10:20 PM CEST Rafael J. Wysocki wrote: > > > >>> On Thu, Jul 5, 2018 at 5:09 PM, Takashi Iwai wrote: > > > >>>> On Thu, 05 Jul 2018 16:00:14 +0200, > > > >>>> Thomas H4nig wrote: > > > >>>>> > > > >>>>> Am 05.07.2018 um 14:12 schrieb Takashi Iwai: > > > >>>>>> On Thu, 05 Jul 2018 12:41:03 +0200, > > > >>>>>> Rafael J. Wysocki wrote: > > > >>>>>>> > > > >>>>>>> On Thursday, July 5, 2018 11:50:11 AM CEST Takashi Iwai wrote: > > > >>>>>>>> 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? > > > >>>>>>> > > > >>>>>>> Basically, yes. > > > >>>>>>> > > > >>>>>>> It looks like a GPE may remain active which then triggers wakeup after > > > >>>>>>> shutdown. > > > >>>>>>> > > > >>>>>>> On a hunch, I'm wondering if reverting commit > > > >>>>>>> > > > >>>>>>> 18996f2db918 ACPICA: Events: Stop unconditionally clearing ACPI IRQs during suspend/resume > > > >>>>>>> > > > >>>>>>> (may not revert clearly, though) makes any difference. > > > >>>>>> > > > >>>>>> OK, I'm building a 4.17.x test kernel with that revert, in OBS > > > >>>>>> home:tiwai:bsc1099930 repo. > > > >>>>>> > > > >>>>>> Thomas, could you try later the kernel in > > > >>>>>> http://download.opensuse.org/repositories/home:/tiwai:/bsc1099930/standard/ > > > >>>>>> ? It'll take an hour or so until the build finishes. > > > >>>>> > > > >>>>> With your new built kernel > > > >>>>> 4.17.4-1.g6f23755-default > > > >>>>> > > > >>>>> the power button works again, so the revert solved the problem > > > >>>> > > > >>>> Thanks, that clarifies the cause. > > > >>>> Adding Erik and Lv to Cc. > > > >>>> > > > >>>> I guess it's the side-effect by removing > > > >>>> acpi_ev_walk_gpe_list(acpi_hw_clear_gpe_block, NULL); > > > >>>> in acpi_hw_disable_all_gpes(). > > > >>>> > > > >>>> This function is called from acpi_power_off_prepare(), and the machine > > > >>>> goes to power off without clearing the GPEs, hence it's woken up later > > > >>>> unexpectedly. > > > >>> > > > >>> That's correct. > > > >>> > > > >>> We need to fix up that commit. I'll try to prepare something. > > > >>> > > > >> > > > >> Below is a patch to test that theory and maybe fix things if it is correct. > > > >> > > > >> What it does is to clear all GPEs after disabling them in > > > >> acpi_power_off_prepare() which should address the issue if our theory > > > >> about the underlying reason is correct. > > > >> > > > >> Please test. > > > > > > > > OK, building a new test kernel package in OBS home:tiwai:bsc1099930-2 > > > > repo. It'll appear at > > > > http://download.opensuse.org/repositories/home:/tiwai:/bsc1099930-2/standard/ > > > > > > > > Thomas, please give it a try later. > > > > > > > > > > > > thanks, > > > > > > > > Takashi > > > > > > I am sorry, but with your test kernel 4.17.4-1.g76c6238-default the > > > notebook again gets not properly powered off but restarts > > > > Interesting. The package version shows that the tested kernel must be > > the right one. (Though, it'd be good to double-check -- it's often > > confusing if you have multiple same kernel versions on the system.) > > > > If Rafael's patch doesn't work, we'd need to identify which change in > > the commit 18996f2db918 has the effect. > > I'd rather prefer the following modification of the previous patch to be > tested: OK, a new test kernel is being built on OBS home:tiwai:bsc1099930-3 repo. The release number will be *.g3ecdf0b. Please give it a try later. thanks, Takashi