Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp535368ybt; Wed, 17 Jun 2020 07:32:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzcZWiFda4CRkCiZxkDTwyp8vL3sZlrOA1twbXcr7H1AAurDkrcBx089IU7iJp1/TGONryr X-Received: by 2002:a17:906:2c44:: with SMTP id f4mr8136635ejh.183.1592404372511; Wed, 17 Jun 2020 07:32:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592404372; cv=none; d=google.com; s=arc-20160816; b=uC4DuYOCKCkE0lAdypBd5kwmABHfeUJpgmrEQgtH4eTiV2SEfz6sIVFZc2oIL2Dogt vVQG/rL1fxQT5doo1KRB/9qyNFRFz341PRBjWoSYwBOIO2kjxzsTSdIiPV8AruyAa3ab n3lLhwt4cfymm7WJZujXvbtygOqiLf2P7T6xaJbmBKLTgDKmxQVuLEucFhg1uYCuUWBb OY42sbn3GFmK7IJ81ePr5A4KJ+xFqe7dtHhZyb69kwUvZwMCPkZqF/+S72KqD1gHtlar PGLzywat3nx4H/MzrzenrzRg1RV1ID38uAp+Mt++v65f9eGLAG1k09wSgADN1dhw5EGZ p00A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=tCsTu8UFtuQfD+kHBvsAecBD5PyGDaWAELFINXFe7wk=; b=XsNqCn8fKk6MZbdo+LtmbU033qTu37/ijm2tcoV9q9AUA7n26YzzSc3/vtnG7x1dVo oxYxWroZZLT/fWrhsHGZ1Pp9SfUPeiWJQxYcEEw28vVqS/bOXT07Tmmq2KjXnynXSop9 s3P7y2M92sLPME5MuOVz5XGsd+hxijSoJ4D4aMOZhdtqhV30oOcRDVITDDCjP/qb9PfE QiER2kkI4U/tolen1KK65u2r39VwHSocO/bvHCrjTxC9gAHNXQ6EUOl9VZUEj21Jk0SY hn1vIhYUTjxc886CM+MGHYGvBHqswu0+omkLw6gAyQ/puIeNFl5x5TG1pqXv61QVf0ku Q5iw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s13si29913edr.576.2020.06.17.07.32.30; Wed, 17 Jun 2020 07:32:52 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726815AbgFQO1l (ORCPT + 99 others); Wed, 17 Jun 2020 10:27:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58932 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725901AbgFQO1k (ORCPT ); Wed, 17 Jun 2020 10:27:40 -0400 Received: from Galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BB2E5C06174E; Wed, 17 Jun 2020 07:27:40 -0700 (PDT) Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1jlZ2M-0002bW-7s; Wed, 17 Jun 2020 16:27:34 +0200 Date: Wed, 17 Jun 2020 16:27:34 +0200 From: Sebastian Andrzej Siewior To: Stephen Berman Cc: Thomas Gleixner , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: power-off delay/hang due to commit 6d25be57 (mainline) Message-ID: <20200617142734.mxwfoblufmo6li5e@linutronix.de> References: <20200612110122.jossn5zrktcvpbpm@linutronix.de> <87tuzdrgm5.fsf@gmx.net> <20200614171005.3zy673p6bpwoqnmq@linutronix.de> <874krcsquv.fsf@gmx.net> <20200615145130.bcdidqkp6w23xb6c@linutronix.de> <87tuzbh482.fsf@gmx.net> <20200616073827.vysntufld3ves666@linutronix.de> <87o8pjh1i0.fsf@gmx.net> <20200616155501.psduxnisltitodme@linutronix.de> <871rmesqkk.fsf@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <871rmesqkk.fsf@gmx.net> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-06-16 22:28:43 [+0200], Stephen Berman wrote: > Your assessment and predictions are right on the mark! perfect. > I'm fine with the thermal.tzp=300 workaround, but it would be good to > find out why this problem started with commit 6d25be57, if my git > bisection was correct, or if it wasn't, then at least somewhere between > 5.1.0 and 5.2.0. Or can you already deduce why? If not, I'd be more > than happy to continue applying any patches or trying any suggestions > you have, if you want to continue debugging this issue. In any case, > thanks for pursuing it to this point. I have no idea why the commit in question should make any difference. Could please apply the tracing patch on v5.1 and send the trace? > Steve Berman Sebastian