thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thermald (Ubuntu) |
Fix Released
|
High
|
Colin Ian King | ||
Trusty |
Fix Released
|
High
|
Colin Ian King | ||
Vivid |
Won't Fix
|
High
|
Colin Ian King | ||
Wily |
Fix Released
|
High
|
Colin Ian King | ||
Xenial |
Fix Released
|
High
|
Colin Ian King |
Bug Description
SRU Justification Wily, Vivid, Trusty
CPU scaling on a class of Intel CPUs is not functioning correctly, causing the CPU to be throttled back to the lowest CPU frequency
[FIX]
Upstream cherry picks, as recommended by Intel
f4e316ef4d8d8c9
18d1574230c6b9b
6749427098434cc
ba4fe1e7bb77d09
Plus 4 changes to allow clean and simpler patching of the above 4 fix to reduce the risk of breaking thermald with a complex backport:
Remove trailing ':' from THD engine failure message
Remove !! from "No coretemp sysfs found"
Add new option for config file
Support target state
Essentially we now have a white list of valid CPUs to run thermald on, so we can exclude the issues on a wider class of CPUs.
[TEST CASE]
With the buggy thermald, CPU is pegged at the lowest CPU frequency. With the fixed thermald, CPU scaling now works.
[REGRESSION POTENTIAL]
We are allowing thermald now to run on a strict set of CPUs, so we are hoping that the whitelist covers the class that we can legitimately run thermald against.
-------
When I boot with this installed frequency scaling is no longer behaving as expected.
It seems that with this installed, the OS loses control of the scaling.
It seems that scaling is performed, though. And very much to the purpose of power saving.
Performance is terrible because of this. And I do mean terrible.
The default governor is powersave.
Setting the governor to performance (yes, on all cores) doesn't seem to change to scaling behavior. The frequency doesn't pass 800MHz.
I would like to use Intel's microcode updates, but I have to have my CPU running at the speed for which it costs so damn much.
Any suggestions?
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: intel-microcode 3.20150121.1
ProcVersionSign
Uname: Linux 4.1.0-2-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jul 31 17:56:39 2015
InstallationDate: Installed on 2010-10-12 (1753 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: intel-microcode
UpgradeStatus: Upgraded to wily on 2014-11-11 (262 days ago)
description: | updated |
Changed in intel-microcode (Ubuntu): | |
status: | Confirmed → In Progress |
importance: | Undecided → High |
assignee: | nobody → Colin Ian King (colin-king) |
summary: |
- Breaks frequency scaling in Xeon® E5-2687W v3 + Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3 |
summary: |
- Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3 + Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 + v3 |
description: | updated |
description: | updated |
description: | updated |
Changed in thermald (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Colin Ian King (colin-king) |
milestone: | none → xenial-updates |
Changed in thermald (Ubuntu Wily): | |
milestone: | none → wily-updates |
assignee: | nobody → Colin Ian King (colin-king) |
importance: | Undecided → High |
summary: |
- Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 - v3 + thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3 |
Changed in thermald (Ubuntu Trusty): | |
assignee: | nobody → Colin Ian King (colin-king) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in thermald (Ubuntu Wily): | |
status: | New → In Progress |
Changed in thermald (Ubuntu Vivid): | |
assignee: | nobody → Colin Ian King (colin-king) |
Changed in thermald (Ubuntu Vivid): | |
importance: | Undecided → High |
milestone: | none → vivid-updates |
status: | New → In Progress |
Changed in thermald (Ubuntu Trusty): | |
milestone: | none → trusty-updates |
description: | updated |
no longer affects: | intel-microcode (Ubuntu) |
no longer affects: | intel-microcode (Ubuntu Trusty) |
no longer affects: | intel-microcode (Ubuntu Vivid) |
no longer affects: | intel-microcode (Ubuntu Wily) |
no longer affects: | intel-microcode (Ubuntu Xenial) |
tags: | added: trusty vivid |
Changed in thermald (Ubuntu): | |
milestone: | xenial-updates → none |
I wonder if it is something like thermald being over-zealous.
Can you try:
sudo systemctl stop thermald
and see if that changes the behaviour