Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp472996pxa; Tue, 11 Aug 2020 07:35:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxk7NI3lOlkiEn/kYiS9I0gbUv6nWvhFFYXDjm/C817EzXoxxD0pKeRUbWE9Nb7fpAOcfGR X-Received: by 2002:a17:906:b890:: with SMTP id hb16mr28131007ejb.376.1597156523071; Tue, 11 Aug 2020 07:35:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597156523; cv=none; d=google.com; s=arc-20160816; b=NBmNGRh45b9zfQu7lXV/8T9RBV03yqZqgTceHxo7MgyCkN41p92o/1QxeEfQf5i+ys l9Va6LYcNGmFHmVOC8pxy8I9dt+5FLKokzsYxesPqvCMJvtTnA9cj+2OKy0mWDU70DhS zrMgZfMOMhiFHpRrcuy13xDfv4L8BL7fGy07i55pAfxR6nI24f+7nng9FJQZPK56hMTc qZsV5bE5Jx8EYVZ9QiA/Va6cXVjm8RHCTVv0S6W9veuWzJz1dThcX7Hy9qsrg7+9BmDW KnJm8JBjs0zeOTvFncW48DTIBQ1fV/1aqFRdGN90mb+eEbOtAyOHEIWjTyhiQM0PHrEj p64g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=KIC4cfW+RcaIaHxzET6Mv7HV0tRxX9+Hs/NGmdFDqgQ=; b=IUpQqK/2xLbXWXXlbr2sebSI78FhsjhtzPoivtSeIIP65omqkrCWD0CRGj/uN9q9jS WcBSselwR8kpU4zgwo96g9h0ugpiA7wzwNhDnT+S3KKEPiVKux9R8KYaOJ3ul02hlOPQ /WiFi3geVt1U7633iTl3K9clMZzSk8kjtBlDFC/uZvQ2DMlxNg4cDNOwvO9mxDWp4Kve vjMEGwuGFFJ2hgNJlxHSJxgUZVg2TrM9Puc7C9SPfAFhEP9g7dIA05Kjr1DBPr+iY7G/ jfYIlLEM84KUN2pxMCOJO0vvD87gXWqT3y5witO51YAzqki8C+aHcRpxJHTpOkFT26PI 3IYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id rl11si11438497ejb.519.2020.08.11.07.34.59; Tue, 11 Aug 2020 07:35:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728768AbgHKOeY (ORCPT + 99 others); Tue, 11 Aug 2020 10:34:24 -0400 Received: from mail-oo1-f67.google.com ([209.85.161.67]:35743 "EHLO mail-oo1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728737AbgHKOeX (ORCPT ); Tue, 11 Aug 2020 10:34:23 -0400 Received: by mail-oo1-f67.google.com with SMTP id j19so2669566oor.2; Tue, 11 Aug 2020 07:34:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KIC4cfW+RcaIaHxzET6Mv7HV0tRxX9+Hs/NGmdFDqgQ=; b=lV041ly4fydpqfzso7qJIM66jjIFILbyLnAFM82OxHw1RPjEyWWhrZPEI5qTFBH350 RVwimoFDQGPBVICZdM0aN3qrQ5LCNztQcaYTBAoIJ9sQwfh0dhlgTRd9zjkuVpjEXMAc K6bIzP+0c2HmORZq1We6vb9jMpCs47iooTJsdnV4SjbQYE9CKqzY/qaiJdX6m4SdS5b3 OedR95VQnwobXqiqI2kj33s0d0AbxMB/jj+C944Gh4EwMgvjLM8zpUqWv+47FEYswhGO 6cV1fQr8+GZFv5Uw1ydwvfDye4VYKkY/DE/G+UZPPGfx+/gLUMi53gX0hwN6e69uvt1C 238g== X-Gm-Message-State: AOAM532yWo/tk/IwTxPqQrfWtMS768FL+cY+sYGoQKMrxk9X0u1T2FEF aEHCfdUcg9M7eOfySrPILtk8XonHzfKE7QmRlV0= X-Received: by 2002:a4a:4201:: with SMTP id h1mr5401194ooj.1.1597156462415; Tue, 11 Aug 2020 07:34:22 -0700 (PDT) MIME-Version: 1.0 References: <871rmesqkk.fsf@gmx.net> <20200617142734.mxwfoblufmo6li5e@linutronix.de> <87ftatqu07.fsf@gmx.net> <20200624201156.xu6hel3drnhno6c3@linutronix.de> <87ftak2kxr.fsf@rub.de> <20200714134410.3odqfvjq6rndjjf6@linutronix.de> <20200714141135.47adndrsdgpiqfy4@linutronix.de> <87blkbx1gt.fsf@gmx.net> <87imdp5r80.fsf@rub.de> <20200811132955.wbt55ns7bu5mxouq@linutronix.de> In-Reply-To: <20200811132955.wbt55ns7bu5mxouq@linutronix.de> From: "Rafael J. Wysocki" Date: Tue, 11 Aug 2020 16:34:09 +0200 Message-ID: Subject: Re: power-off delay/hang due to commit 6d25be57 (mainline) To: Sebastian Andrzej Siewior Cc: Stephen Berman , "Rafael J. Wysocki" , Zhang Rui , Robert Moore , Erik Kaneda , "Rafael J. Wysocki" , Len Brown , Thomas Gleixner , Peter Zijlstra , Linux Kernel Mailing List , ACPI Devel Maling List , "open list:ACPI COMPONENT ARCHITECTURE (ACPICA)" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 11, 2020 at 3:29 PM Sebastian Andrzej Siewior wrote: > > On 2020-08-11 13:58:39 [+0200], Stephen Berman wrote: > > him about your workaround of adding 'thermal.tzp=300' to the kernel > > commandline, and he replied that this works for him too. And it turns > > out we have similar motherboards: I have a Gigabyte Z390 M Gaming > > Rev. 1001 board and he has Gigabyte Z390 Designare rev 1.0. > > Yes. Based on latest dmesg, the ACPI tables contain code which schedules > the worker and takes so long. It is possible / likely that his board > contains the same tables which leads to the same effect. After all those > two boards are very similar from the naming part :) > Would you mind to dump the ACPI tables and send them? There might be > some hints. Do we have a BZ for this? It would be useful to open one if not. > It might be possible that a BIOS update fixes the problem but I would > prefer very much to fix this in kernel to ensure that such a BIOS does > not lead to this problem again. I agree. It looks like one way to address this issue might be to add a rate limit for thermal notifications on a given zone.