Bug 2194421

Summary:	thermald service requires --workaround-enabled
Product:	[Fedora] Fedora	Reporter:	Luke Jones <luke>
Component:	thermald	Assignee:	Benjamin Berg <benjamin-fedora>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	38	CC:	bberg, benjamin-fedora, besser82, christian, ckellner
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	thermald-2.5.6-1.fc38 thermald-2.5.6-1.fc39	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-02-20 01:37:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Luke Jones 2023-05-06 01:20:17 UTC

Quite a few laptops from ASUS and others are having their frequency limited by 1000Mhz less than max depending on the workload.

For example:

System 1 is stressing all cores. The e-cores are being limited to 2200Mhz and the p-cores are being limited to 3200Mhz or less. Single core performance is able to reach the proper max frequency of 5000Mhz.

After applying `--workaround-enabled` to thermald (added to thermald.service and restarted) the e-cores can then reach 3200Mhz, and the p-cores can hit 4200Mhz when all cores are stressed. As heat saturation reaches peak the Mhz does drop, but only to 3800Mhz which is much much better than previous behaviour.

My test laptop is `12th Gen Intel i9-12900H (20) @ 4.900GHz`

Many others in my discord for asus-linux have experienced similar behaviour.

Comment 1 Luke Jones 2023-06-19 07:25:47 UTC

For many many new Intel laptops they need a build of thermald from here - https://github.com/intel/thermal_daemon

Without this they are running up to 1500Mhz less boost depending on load.

Comment 2 Fedora Update System 2024-02-11 18:13:34 UTC

FEDORA-2024-dd2f4f938d (thermald-2.5.6-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-dd2f4f938d

Comment 3 Fedora Update System 2024-02-11 18:13:40 UTC

FEDORA-2024-4a57c10b1e (thermald-2.5.6-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-4a57c10b1e

Comment 4 Fedora Update System 2024-02-12 01:52:14 UTC

FEDORA-2024-4a57c10b1e has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4a57c10b1e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4a57c10b1e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-02-12 02:42:45 UTC

FEDORA-2024-dd2f4f938d has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-dd2f4f938d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-dd2f4f938d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-02-20 01:37:25 UTC

FEDORA-2024-dd2f4f938d (thermald-2.5.6-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2024-02-20 01:39:24 UTC

FEDORA-2024-4a57c10b1e (thermald-2.5.6-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.