CPU frequency too high even with 'powersave' governor
Recently I noticed my CPU sits most of the time at high frequencies, even with very little load.
It is an i5-7300HQ processor which should use frequencies between 800 MHz and 2.5 GHz (3.5 GHz with Turbo Boost).
Now even when load is about 2-8%, the frequencies I see are usually between 2.6 and 3.2 GHz, which means the CPU is almost always Turbo Boosting.
Before it was always 900 - 1200 MHz.
The scaling governor is set to powersave:
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
powersave
powersave
powersave
In /etc/default/grub
I have a line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=disable scsi_mod.scan=sync"
In /etc/default/cpufrequtils
:
GOVERNOR="powersave"
There is no /sys/devices/system/cpu/intel_pstate/
dir
My system specs are:
- Laptop: HP Pavilion - 15-bc203nw
- OS: Ubuntu (Xubuntu) 18.04.1 LTS
- CPU: Intel Core i5-7300HQ
EDIT
After @WinEunuuchs2Unix suggestions I again have /sys/devices/system/cpu/intel_pstate/
dir.
Typing the following:
cd /sys/devices/system/cpu/cpu0/cpufreq && paste <(ls *) <(cat *)
gives the output:
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 3236541
scaling_driver intel_pstate
scaling_governor performance
scaling_max_freq 3500000
scaling_min_freq 3500000
scaling_setspeed <unsupported>
How can I set it to powersave
(just changing it in scaling_governor
file doesn't do anything).
18.04 intel cpu cpufreq governor
add a comment |
Recently I noticed my CPU sits most of the time at high frequencies, even with very little load.
It is an i5-7300HQ processor which should use frequencies between 800 MHz and 2.5 GHz (3.5 GHz with Turbo Boost).
Now even when load is about 2-8%, the frequencies I see are usually between 2.6 and 3.2 GHz, which means the CPU is almost always Turbo Boosting.
Before it was always 900 - 1200 MHz.
The scaling governor is set to powersave:
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
powersave
powersave
powersave
In /etc/default/grub
I have a line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=disable scsi_mod.scan=sync"
In /etc/default/cpufrequtils
:
GOVERNOR="powersave"
There is no /sys/devices/system/cpu/intel_pstate/
dir
My system specs are:
- Laptop: HP Pavilion - 15-bc203nw
- OS: Ubuntu (Xubuntu) 18.04.1 LTS
- CPU: Intel Core i5-7300HQ
EDIT
After @WinEunuuchs2Unix suggestions I again have /sys/devices/system/cpu/intel_pstate/
dir.
Typing the following:
cd /sys/devices/system/cpu/cpu0/cpufreq && paste <(ls *) <(cat *)
gives the output:
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 3236541
scaling_driver intel_pstate
scaling_governor performance
scaling_max_freq 3500000
scaling_min_freq 3500000
scaling_setspeed <unsupported>
How can I set it to powersave
(just changing it in scaling_governor
file doesn't do anything).
18.04 intel cpu cpufreq governor
If you are not using the intel_pstate CPU frequency driver, then it should be using the acpi-cpufreq driver by default. That driver using the powersave governor should always be a the minimum CPU frequency. So that is odd. Anyway, I agree with @WinEunuuchs2Unix 's answer.
– Doug Smythies
Dec 16 at 15:25
add a comment |
Recently I noticed my CPU sits most of the time at high frequencies, even with very little load.
It is an i5-7300HQ processor which should use frequencies between 800 MHz and 2.5 GHz (3.5 GHz with Turbo Boost).
Now even when load is about 2-8%, the frequencies I see are usually between 2.6 and 3.2 GHz, which means the CPU is almost always Turbo Boosting.
Before it was always 900 - 1200 MHz.
The scaling governor is set to powersave:
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
powersave
powersave
powersave
In /etc/default/grub
I have a line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=disable scsi_mod.scan=sync"
In /etc/default/cpufrequtils
:
GOVERNOR="powersave"
There is no /sys/devices/system/cpu/intel_pstate/
dir
My system specs are:
- Laptop: HP Pavilion - 15-bc203nw
- OS: Ubuntu (Xubuntu) 18.04.1 LTS
- CPU: Intel Core i5-7300HQ
EDIT
After @WinEunuuchs2Unix suggestions I again have /sys/devices/system/cpu/intel_pstate/
dir.
Typing the following:
cd /sys/devices/system/cpu/cpu0/cpufreq && paste <(ls *) <(cat *)
gives the output:
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 3236541
scaling_driver intel_pstate
scaling_governor performance
scaling_max_freq 3500000
scaling_min_freq 3500000
scaling_setspeed <unsupported>
How can I set it to powersave
(just changing it in scaling_governor
file doesn't do anything).
18.04 intel cpu cpufreq governor
Recently I noticed my CPU sits most of the time at high frequencies, even with very little load.
It is an i5-7300HQ processor which should use frequencies between 800 MHz and 2.5 GHz (3.5 GHz with Turbo Boost).
Now even when load is about 2-8%, the frequencies I see are usually between 2.6 and 3.2 GHz, which means the CPU is almost always Turbo Boosting.
Before it was always 900 - 1200 MHz.
The scaling governor is set to powersave:
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
powersave
powersave
powersave
In /etc/default/grub
I have a line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=disable scsi_mod.scan=sync"
In /etc/default/cpufrequtils
:
GOVERNOR="powersave"
There is no /sys/devices/system/cpu/intel_pstate/
dir
My system specs are:
- Laptop: HP Pavilion - 15-bc203nw
- OS: Ubuntu (Xubuntu) 18.04.1 LTS
- CPU: Intel Core i5-7300HQ
EDIT
After @WinEunuuchs2Unix suggestions I again have /sys/devices/system/cpu/intel_pstate/
dir.
Typing the following:
cd /sys/devices/system/cpu/cpu0/cpufreq && paste <(ls *) <(cat *)
gives the output:
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 3236541
scaling_driver intel_pstate
scaling_governor performance
scaling_max_freq 3500000
scaling_min_freq 3500000
scaling_setspeed <unsupported>
How can I set it to powersave
(just changing it in scaling_governor
file doesn't do anything).
18.04 intel cpu cpufreq governor
18.04 intel cpu cpufreq governor
edited Dec 16 at 16:16
asked Dec 16 at 13:15
Jorengarenar
184
184
If you are not using the intel_pstate CPU frequency driver, then it should be using the acpi-cpufreq driver by default. That driver using the powersave governor should always be a the minimum CPU frequency. So that is odd. Anyway, I agree with @WinEunuuchs2Unix 's answer.
– Doug Smythies
Dec 16 at 15:25
add a comment |
If you are not using the intel_pstate CPU frequency driver, then it should be using the acpi-cpufreq driver by default. That driver using the powersave governor should always be a the minimum CPU frequency. So that is odd. Anyway, I agree with @WinEunuuchs2Unix 's answer.
– Doug Smythies
Dec 16 at 15:25
If you are not using the intel_pstate CPU frequency driver, then it should be using the acpi-cpufreq driver by default. That driver using the powersave governor should always be a the minimum CPU frequency. So that is odd. Anyway, I agree with @WinEunuuchs2Unix 's answer.
– Doug Smythies
Dec 16 at 15:25
If you are not using the intel_pstate CPU frequency driver, then it should be using the acpi-cpufreq driver by default. That driver using the powersave governor should always be a the minimum CPU frequency. So that is odd. Anyway, I agree with @WinEunuuchs2Unix 's answer.
– Doug Smythies
Dec 16 at 15:25
add a comment |
1 Answer
1
active
oldest
votes
Answer Version 2.0
OP updated question with results of Initial Answer below and for whatever reason the governor is set to performance
mode which runs all CPU's at max speed all the time.
We need to do the reverse of this answer: Set CPU governor to performance in 18.04:
Use: sudo -H gedit /etc/rc.local
put insert this before the last line containing exit 0
:
sleep 120 # Give CPU startup routines time to settle.
echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
echo 800000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
Save the file and reboot. Two minutes after rebooting your CPU's will settle down and run normally.
What if /etc/rc.local
doesn't exist?
From this: Ubuntu 16.10 rc.local file does not exist
you need to enter:
sudo systemctl enable rc-local.service
Initial Answer
According to: intel_pstate
CPU Performance Scaling Driver, intel_pstate
status should be:
status
Operation mode of the driver: “active”, “passive” or “off”.
“active”
The driver is functional and in the active mode.
“passive”
The driver is functional and in the passive mode.
“off”
The driver is not functional (it is not registered as a scaling driver with the CPUFreq core)
My first step would be to remove your kernel command line parameter intel_pstate=disable
.
Reboot and type the following:
$ cd /sys/devices/system/cpu/cpu0/cpufreq
$ paste <(ls *) <(cat *)
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 832522
scaling_driver intel_pstate
scaling_governor powersave
scaling_max_freq 3500000
scaling_min_freq 800000
scaling_setspeed <unsupported>
This is what I have in a default configuration without intel_pstate=disable
.
Pay close attention to scaling_max_freq
and scaling_min_freq
.
You might want to temporarily uninstall CPU Freq Utils package:
sudo apt remove cpufrequtils
I have never found a need for it and it might be mucking your system up. Later you can install it again (if need be) with:
sudo apt install cpufrequtils
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102311%2fcpu-frequency-too-high-even-with-powersave-governor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Answer Version 2.0
OP updated question with results of Initial Answer below and for whatever reason the governor is set to performance
mode which runs all CPU's at max speed all the time.
We need to do the reverse of this answer: Set CPU governor to performance in 18.04:
Use: sudo -H gedit /etc/rc.local
put insert this before the last line containing exit 0
:
sleep 120 # Give CPU startup routines time to settle.
echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
echo 800000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
Save the file and reboot. Two minutes after rebooting your CPU's will settle down and run normally.
What if /etc/rc.local
doesn't exist?
From this: Ubuntu 16.10 rc.local file does not exist
you need to enter:
sudo systemctl enable rc-local.service
Initial Answer
According to: intel_pstate
CPU Performance Scaling Driver, intel_pstate
status should be:
status
Operation mode of the driver: “active”, “passive” or “off”.
“active”
The driver is functional and in the active mode.
“passive”
The driver is functional and in the passive mode.
“off”
The driver is not functional (it is not registered as a scaling driver with the CPUFreq core)
My first step would be to remove your kernel command line parameter intel_pstate=disable
.
Reboot and type the following:
$ cd /sys/devices/system/cpu/cpu0/cpufreq
$ paste <(ls *) <(cat *)
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 832522
scaling_driver intel_pstate
scaling_governor powersave
scaling_max_freq 3500000
scaling_min_freq 800000
scaling_setspeed <unsupported>
This is what I have in a default configuration without intel_pstate=disable
.
Pay close attention to scaling_max_freq
and scaling_min_freq
.
You might want to temporarily uninstall CPU Freq Utils package:
sudo apt remove cpufrequtils
I have never found a need for it and it might be mucking your system up. Later you can install it again (if need be) with:
sudo apt install cpufrequtils
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
add a comment |
Answer Version 2.0
OP updated question with results of Initial Answer below and for whatever reason the governor is set to performance
mode which runs all CPU's at max speed all the time.
We need to do the reverse of this answer: Set CPU governor to performance in 18.04:
Use: sudo -H gedit /etc/rc.local
put insert this before the last line containing exit 0
:
sleep 120 # Give CPU startup routines time to settle.
echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
echo 800000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
Save the file and reboot. Two minutes after rebooting your CPU's will settle down and run normally.
What if /etc/rc.local
doesn't exist?
From this: Ubuntu 16.10 rc.local file does not exist
you need to enter:
sudo systemctl enable rc-local.service
Initial Answer
According to: intel_pstate
CPU Performance Scaling Driver, intel_pstate
status should be:
status
Operation mode of the driver: “active”, “passive” or “off”.
“active”
The driver is functional and in the active mode.
“passive”
The driver is functional and in the passive mode.
“off”
The driver is not functional (it is not registered as a scaling driver with the CPUFreq core)
My first step would be to remove your kernel command line parameter intel_pstate=disable
.
Reboot and type the following:
$ cd /sys/devices/system/cpu/cpu0/cpufreq
$ paste <(ls *) <(cat *)
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 832522
scaling_driver intel_pstate
scaling_governor powersave
scaling_max_freq 3500000
scaling_min_freq 800000
scaling_setspeed <unsupported>
This is what I have in a default configuration without intel_pstate=disable
.
Pay close attention to scaling_max_freq
and scaling_min_freq
.
You might want to temporarily uninstall CPU Freq Utils package:
sudo apt remove cpufrequtils
I have never found a need for it and it might be mucking your system up. Later you can install it again (if need be) with:
sudo apt install cpufrequtils
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
add a comment |
Answer Version 2.0
OP updated question with results of Initial Answer below and for whatever reason the governor is set to performance
mode which runs all CPU's at max speed all the time.
We need to do the reverse of this answer: Set CPU governor to performance in 18.04:
Use: sudo -H gedit /etc/rc.local
put insert this before the last line containing exit 0
:
sleep 120 # Give CPU startup routines time to settle.
echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
echo 800000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
Save the file and reboot. Two minutes after rebooting your CPU's will settle down and run normally.
What if /etc/rc.local
doesn't exist?
From this: Ubuntu 16.10 rc.local file does not exist
you need to enter:
sudo systemctl enable rc-local.service
Initial Answer
According to: intel_pstate
CPU Performance Scaling Driver, intel_pstate
status should be:
status
Operation mode of the driver: “active”, “passive” or “off”.
“active”
The driver is functional and in the active mode.
“passive”
The driver is functional and in the passive mode.
“off”
The driver is not functional (it is not registered as a scaling driver with the CPUFreq core)
My first step would be to remove your kernel command line parameter intel_pstate=disable
.
Reboot and type the following:
$ cd /sys/devices/system/cpu/cpu0/cpufreq
$ paste <(ls *) <(cat *)
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 832522
scaling_driver intel_pstate
scaling_governor powersave
scaling_max_freq 3500000
scaling_min_freq 800000
scaling_setspeed <unsupported>
This is what I have in a default configuration without intel_pstate=disable
.
Pay close attention to scaling_max_freq
and scaling_min_freq
.
You might want to temporarily uninstall CPU Freq Utils package:
sudo apt remove cpufrequtils
I have never found a need for it and it might be mucking your system up. Later you can install it again (if need be) with:
sudo apt install cpufrequtils
Answer Version 2.0
OP updated question with results of Initial Answer below and for whatever reason the governor is set to performance
mode which runs all CPU's at max speed all the time.
We need to do the reverse of this answer: Set CPU governor to performance in 18.04:
Use: sudo -H gedit /etc/rc.local
put insert this before the last line containing exit 0
:
sleep 120 # Give CPU startup routines time to settle.
echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
echo 800000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
Save the file and reboot. Two minutes after rebooting your CPU's will settle down and run normally.
What if /etc/rc.local
doesn't exist?
From this: Ubuntu 16.10 rc.local file does not exist
you need to enter:
sudo systemctl enable rc-local.service
Initial Answer
According to: intel_pstate
CPU Performance Scaling Driver, intel_pstate
status should be:
status
Operation mode of the driver: “active”, “passive” or “off”.
“active”
The driver is functional and in the active mode.
“passive”
The driver is functional and in the passive mode.
“off”
The driver is not functional (it is not registered as a scaling driver with the CPUFreq core)
My first step would be to remove your kernel command line parameter intel_pstate=disable
.
Reboot and type the following:
$ cd /sys/devices/system/cpu/cpu0/cpufreq
$ paste <(ls *) <(cat *)
affected_cpus 0
cpuinfo_max_freq 3500000
cpuinfo_min_freq 800000
cpuinfo_transition_latency 0
energy_performance_available_preferences default performance balance_performance balance_power power
energy_performance_preference balance_performance
related_cpus 0
scaling_available_governors performance powersave
scaling_cur_freq 832522
scaling_driver intel_pstate
scaling_governor powersave
scaling_max_freq 3500000
scaling_min_freq 800000
scaling_setspeed <unsupported>
This is what I have in a default configuration without intel_pstate=disable
.
Pay close attention to scaling_max_freq
and scaling_min_freq
.
You might want to temporarily uninstall CPU Freq Utils package:
sudo apt remove cpufrequtils
I have never found a need for it and it might be mucking your system up. Later you can install it again (if need be) with:
sudo apt install cpufrequtils
edited Dec 17 at 22:00
answered Dec 16 at 15:16
WinEunuuchs2Unix
43.3k1075164
43.3k1075164
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
add a comment |
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
Let us continue this discussion in chat.
– Doug Smythies
Dec 17 at 16:32
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102311%2fcpu-frequency-too-high-even-with-powersave-governor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If you are not using the intel_pstate CPU frequency driver, then it should be using the acpi-cpufreq driver by default. That driver using the powersave governor should always be a the minimum CPU frequency. So that is odd. Anyway, I agree with @WinEunuuchs2Unix 's answer.
– Doug Smythies
Dec 16 at 15:25