From: James Feeney <james@nurealm.net>
To: Borislav Petkov <bp@suse.de>
Cc: linux-smp@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
lkml <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
x86-ml <x86@kernel.org>
Subject: Re: [PATCH] x86/thermal: Fix LVT thermal setup for SMI delivery mode
Date: Fri, 28 May 2021 01:05:14 -0600 [thread overview]
Message-ID: <e23ae63a-8b5b-f2e7-1037-05808a4d08df@nurealm.net> (raw)
In-Reply-To: <YK905sC/2cVOYo6I@zn.tnic>
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
next prev parent reply other threads:[~2021-05-28 7:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a9599b2-f4fe-af9b-90f5-af39c315ec2f@nurealm.net>
2021-05-17 8:32 ` linux 5.12 - fails to boot - soft lockup - CPU#0 stuck for 23s! - RIP smp_call_function_single Borislav Petkov
2021-05-19 3:58 ` James Feeney
2021-05-19 11:12 ` Borislav Petkov
2021-05-19 20:03 ` James Feeney
2021-05-19 21:18 ` Borislav Petkov
2021-05-20 3:12 ` James Feeney
2021-05-20 9:21 ` Borislav Petkov
2021-05-21 22:11 ` James Feeney
2021-05-22 9:06 ` Borislav Petkov
2021-05-22 23:28 ` James Feeney
2021-05-23 17:05 ` Borislav Petkov
2021-05-23 23:02 ` James Feeney
2021-05-24 7:51 ` Borislav Petkov
2021-05-25 4:02 ` James Feeney
2021-05-27 10:31 ` [PATCH] x86/thermal: Fix LVT thermal setup for SMI delivery mode Borislav Petkov
2021-05-27 11:49 ` Thomas Gleixner
2021-05-27 11:56 ` Borislav Petkov
2021-05-27 18:54 ` Borislav Petkov
2021-05-28 8:23 ` Thomas Gleixner
2021-05-28 11:19 ` Borislav Petkov
2021-05-31 18:26 ` James Feeney
2021-05-27 18:09 ` Srinivas Pandruvada
2021-05-27 19:01 ` Borislav Petkov
2021-05-27 20:28 ` Srinivas Pandruvada
2021-05-28 7:05 ` James Feeney [this message]
2021-05-31 21:46 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e23ae63a-8b5b-f2e7-1037-05808a4d08df@nurealm.net \
--to=james@nurealm.net \
--cc=axboe@kernel.dk \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).