From: "Doug Smythies" <dsmythies@telus.net>
To: "'Sergey Senozhatsky'" <senozhatsky@chromium.org>
Cc: "'Rafael J. Wysocki'" <rafael@kernel.org>,
"'Christian Loehle'" <christian.loehle@arm.com>,
"'Rafael J. Wysocki'" <rafael.j.wysocki@intel.com>,
"'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
"'Artem Bityutskiy'" <artem.bityutskiy@linux.intel.com>,
"'Sasha Levin'" <sashal@kernel.org>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"'Tomasz Figa'" <tfiga@chromium.org>, <stable@vger.kernel.org>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: stable: commit "cpuidle: menu: Avoid discarding useful information" causes regressions
Date: Wed, 15 Oct 2025 07:11:41 -0700 [thread overview]
Message-ID: <001601dc3ddd$a19f9850$e4dec8f0$@telus.net> (raw)
In-Reply-To: <sw4p2hk4ofyyz3ncnwi3qs36yc2leailqmal5kksozodkak2ju@wfpqlwep7aid>
On 2025.10.14 21:50 Sergey Senozhatsky wrote:
> On (25/10/14 20:41), Doug Smythies wrote:
>> What thermal limiting methods are being used? Is idle injection being used? Or CPU frequency limiting or both.
>
> How do I find out?
From the turbostat data you do not appear to be using the TCC offset method. This line:
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x0f690080 (105 C)
whereas on my test computer, using the TCC offset method, shows:
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x14641422 (80 C) (100 default - 20 offset)
To check if thermal is being used do:
systemctl status thermal
Example:
doug@s19:~/idle/teo/menu2$ systemctl status thermald
○ thermald.service - Thermal Daemon Service
Loaded: loaded (/usr/lib/systemd/system/thermald.service; disabled; preset: enabled)
Active: inactive (dead)
If something else is being used, I don't know.
... Doug
next prev parent reply other threads:[~2025-10-15 14:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 7:43 stable: commit "cpuidle: menu: Avoid discarding useful information" causes regressions Sergey Senozhatsky
2025-10-14 7:47 ` Greg Kroah-Hartman
2025-10-14 7:54 ` Sergey Senozhatsky
2025-10-14 8:02 ` Greg Kroah-Hartman
2025-10-14 11:08 ` Sergey Senozhatsky
2025-10-14 9:50 ` Christian Loehle
2025-10-14 10:23 ` Sergey Senozhatsky
2025-10-14 10:25 ` Christian Loehle
2025-10-14 11:55 ` Sergey Senozhatsky
2025-10-14 15:11 ` Christian Loehle
2025-10-14 15:54 ` Rafael J. Wysocki
2025-10-14 17:19 ` Christian Loehle
2025-10-14 17:32 ` Rafael J. Wysocki
2025-10-14 17:50 ` Rafael J. Wysocki
2025-10-15 1:29 ` Sergey Senozhatsky
2025-10-15 3:41 ` Doug Smythies
2025-10-15 4:50 ` Sergey Senozhatsky
2025-10-15 14:11 ` Doug Smythies [this message]
2025-10-16 4:59 ` Sergey Senozhatsky
2025-10-16 9:48 ` Rafael J. Wysocki
2025-10-16 10:00 ` Sergey Senozhatsky
2025-10-16 10:05 ` Rafael J. Wysocki
2025-10-15 11:49 ` Rafael J. Wysocki
2025-10-15 14:32 ` Doug Smythies
2025-10-16 9:50 ` Rafael J. Wysocki
2025-10-15 12:31 ` Rafael J. Wysocki
2025-10-16 4:57 ` Sergey Senozhatsky
2025-10-15 1:33 ` Sergey Senozhatsky
2025-10-14 13:47 ` Rafael J. Wysocki
2025-10-14 13:56 ` Sergey Senozhatsky
2025-10-14 13:58 ` Christian Loehle
2025-10-14 14:02 ` Rafael J. Wysocki
2025-10-15 1:56 ` Sergey Senozhatsky
2025-10-15 13:08 ` Rafael J. Wysocki
2025-10-16 4:54 ` Sergey Senozhatsky
2025-10-16 9:47 ` Rafael J. Wysocki
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='001601dc3ddd$a19f9850$e4dec8f0$@telus.net' \
--to=dsmythies@telus.net \
--cc=artem.bityutskiy@linux.intel.com \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=sashal@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tfiga@chromium.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