Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp293153pxj; Fri, 28 May 2021 04:14:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxvNgXx5aIrZqubSi3BG4rmccKFq+JZsZJaaKXknALW4/AEYuUHICrecDd1Q0gPvFlhmfCP X-Received: by 2002:a17:907:10c7:: with SMTP id rv7mr8430994ejb.125.1622200474327; Fri, 28 May 2021 04:14:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622200474; cv=none; d=google.com; s=arc-20160816; b=zmmniyJ7YSYxoRtdEossAfcbnHVUYUAQFYNVSHq/GvRJM0Dl91LLG4N6VdZ1PxCzro 2JxjCmgLz3p2qcsOQ5cEracKhMsAEyXIdXpFlU0CEutmMUkOD/4B7B3BiAoMVZtD+g8g WIbOVV19vICKsUtpRGxiq8YTQPom/yR3HpvXowvRrASFwBp+2Sho+O8PH2tQEy/7spIj lQqt/tHKMJRp+GrFuD9NHuRIgqiXolsLzXLyRXdgjKp/zdi3ooZRsiPxTt7YyqAm95FK SODVg3akKWqYefyCveWW0sVZ5HOXkSyO92hczSPvSvK06l0LN+/5/xX0fSaM8lIuukPE J44g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:reply-to:dkim-signature; bh=A2OZUP7oixGv9GS34bKrt3L2kgQ0JqLmXuT5mLmdGfc=; b=jbaX2lXwKXydwEgGExEoDBgkgYqxY0loJRO927Bvwa2FkrxwHptD5SUUHhb0CeJr5r YoQWkgkWuOxeVSR8ReEdTCiCVYkKxJl/cQ5dT6g1CT4zCTKwAAgz+IzMZshgEpu/cCET CNdBeDkw+QVpyhBvis10yBPc/bIPGBpzyIJ1JUVPKc6Hth+iGN7Dqt3xfaLqj1ST7Ee1 KCc74/gKrH3Kcjdtb9d6HbIWODwX9A1oFYxge3mx9NNlkFQov+hQTC/6larcNtrgTZaQ YvQ/Jig1PtYny+Y9tTCceuPL3AOY4WFkUc6tqKTGkJQzTmzhRxqlzJR8lMwx4WuPPqVT E1cA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@comcastmailservice.net header.s=20180828_2048 header.b=qXw82WJL; 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 f19si3452899ejr.484.2021.05.28.04.14.10; Fri, 28 May 2021 04:14:34 -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; dkim=pass header.i=@comcastmailservice.net header.s=20180828_2048 header.b=qXw82WJL; 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 S230057AbhE1HG4 (ORCPT + 99 others); Fri, 28 May 2021 03:06:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45892 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229574AbhE1HGz (ORCPT ); Fri, 28 May 2021 03:06:55 -0400 Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D11EAC061574 for ; Fri, 28 May 2021 00:05:20 -0700 (PDT) Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-01v.sys.comcast.net with ESMTP id mWWIlAUUKfFsMmWYYlnd7a; Fri, 28 May 2021 07:05:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1622185518; bh=A2OZUP7oixGv9GS34bKrt3L2kgQ0JqLmXuT5mLmdGfc=; h=Received:Received:Reply-To:Subject:To:From:Message-ID:Date: MIME-Version:Content-Type; b=qXw82WJL6JAmljyjQF1NzjCNhz9ZHw8XqxqEmk9se4gne7myX35Se4gx6Hnc202i5 gzBZSS8IzqqQzTKYn14lCXx/eqEfODMPCmS7eJQArk7NrsHAvPu1pZ08a3heYtHSTB yoYKLHVdRRv4gVkJ2VUuAG1xAQtlP2DhU2x7Cgkx3VaYTZyrQaNc6RCeirMvz8xGFy vY1ofrm8JRuX8qCjQOTOxUJmNNI+IdZuoYq9dYRXEH+HX5+aDVsPwANaDd75ocUsW+ 65GpTsbV4jA5PMOXQrpVRmaVol814xuJl/l/emNGNkumxlETUL8rNgbTKYEiwuCpkp Yk+rmcd85UYMg== Received: from [IPv6:2001:558:6040:22:2171:426f:b27e:296d] ([IPv6:2001:558:6040:22:2171:426f:b27e:296d]) by resomta-ch2-20v.sys.comcast.net with ESMTPSA id mWYVlCY0SnYgZmWYWlA4Lp; Fri, 28 May 2021 07:05:17 +0000 X-Xfinity-VMeta: sc=-100.00;st=legit Reply-To: james@nurealm.net Subject: Re: [PATCH] x86/thermal: Fix LVT thermal setup for SMI delivery mode To: Borislav Petkov Cc: linux-smp@vger.kernel.org, Jens Axboe , lkml , Zhang Rui , Srinivas Pandruvada , x86-ml References: <373464e3-b8a0-0fe0-b890-41df0eecf090@nurealm.net> <1f6c70f4-6680-d6ea-465a-548dc7698317@nurealm.net> From: James Feeney Message-ID: Date: Fri, 28 May 2021 01:05:14 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/27/21 4:31 AM, Borislav Petkov wrote: > it took me a while to find a box like yours to reproduce on. Anyway, > here's what looks like the final fix, you could give it a run. Going through the motions, I can confirm "no surprises". The final patch is working as expected, with both full power-off boots and "warm" reboots. On 5/27/21 12:09 PM, Srinivas Pandruvada wrote: > My guess is that system is booting hot sometimes. SMM started fan or > some cooling and set a temperature threshold. It is waiting for thermal > interrupt for temperature threshold, which it never got. I remind, that when the boot would hang at "Trying to unpack rootfs image as initramfs...", then if the machine is let sit in this state, the fan will begin to run full, off and on, suggesting that maybe the processor is still running and running full power. Something - maybe the management engine? - is still running, and able to cycle the fan speed, high and low. There *must*, then, be "high" and "low" temperature thresholds being reached, as the fan speed cycles, and there is *no* continuation of the boot process when either of these thresholds is reached. So that interpretation - waiting for thermal interrupt - does not seem to address all the circumstances. James