CPU temperatures in linux: throttling or wrong reading?












3















Using a Lenovo Legion Y520 with i7-7700HQ (base clock 2.8Ghz) and GTX 1050.



I'm getting CPU overheating warnings in linux and it's affecting my performance in games (found in Payday 2 and CS:GO). I've never had problems in Windows.



This is what I found when trying to troubleshoot this issue:



In Windows 10 (using aida64)




  • Windows stays at around 3.4 Ghz on idle (no idea why this is so high with less than 3% cpu usage), with a temperature of around 50C.


  • When stressing the cpu, the temperature goes slowly from about 50C to around 75C and stays there comfortably. Clock speeds are about 2.9Ghz when stressing. Utilization is always 100%. Aida64 doesn't report throttling. The voltage on the CPU core coes from about 1.1 to 0.9 when stressing.



In Arch Linux (using s-tui)




  • Linux stays at around 2.0Ghz on idle, with a temperature of around 50C.


  • Here's where it gets weird: when stressing the cpu, the temperature IMMEDIATELY goes from 50C to about 93C. Clock speeds are exactly 3.4Ghz when stressing. Utilization is always 100%. When turing the stress test off, the temperature IMMEDIATELY goes back to about 50C, as if nothing ever happened. The laptop certainly doesn't feel like it heats up to 90C+ when doing this, even after a long stress.



Here's an image that shows how temperature, power, and frequency all go down at the exact same time. Notice how much cpu temperature changes in so little time.
Image of throttling in linux



How do I fix this throttling issue? Do I undervolt my CPU in linux? How come it reads temperatures wrong in Linux but not in Windows?



I changed the profile using cpupower from powersave to performance. I still see the same throttling in s-tui. There is a jump up in idle cpu frequency when setting to performance (instead of around 2000-2500Mhz to always at 3400Mhz), but that's the only thing that has changed.



Fan control



I tried to control fans using fancontrol (lm_sensors), but pwmconfig says there are no pwm-capable sensor modules installed.



I tried it with NBFC, but it doesn't seem to be doing anything, no matter what profile I choose. I don't even know if NBFC can control my fans, but it doesn't report any errors when choosing a profile.



I also tried thinkfan, which can control my fans, but it doesn't seem to help with throttling.



Solution



I found that lowering the maximum allowed cpu frequency using cpupower to something like 3100MHz instead of the default 3800 fixes all issues.



sudo cpupower frequency-set -u 3100MHz



I also changed max_freq in /etc/default/cpupower to the same value, to make it permanent. I found that this does result in a slight fps drop in games, but nothing serious. At least my fps is stable :)



Sadly I think this might result in decreased performance in non-gaming tasks like when compiling something.










share|improve this question




















  • 1





    Yes temperatures on microchips can jump really high almost instantaneously depending on if/how they are cooled, especially when using up lots of power. Ever touched a running CPU? I don't recommend it. Additionally, the high performance profile could still be scaling the frequency down during parts of the stress test that aren't using as much number crunching. Source: am computer engineer

    – Jeff A
    Jan 2 at 22:59













  • Thanks for the explanation. So how can I eliminate throttling when both powersave and performance don't help against throttling?

    – zjeffer
    Jan 3 at 0:05













  • If I had to take a guess, I'd say you need better cooling while you are putting high stress on the CPU/GPU. I can't really vouch for the temperature sensors and whether they actually function properly on Linux -- every motherboard is different. If you have some extra cash try getting a gaming laptop cooling pad with a bunch of fans on it. The scaling/lagging could be happening due to temperature spikes. You really want to stay below 80 degrees Celsius at all times

    – Jeff A
    Jan 3 at 0:16






  • 1





    I was thinking that maybe linux isn't turning all your fans up to the proper speed when things get hot, leading to the throttling. Have you messed around with programs that would let you control the fan speed and just put them on full blast before stress testing or gaming?

    – Jeff A
    Jan 3 at 2:55






  • 1





    I reformatted the whole post so other people can more easily find a solution if they have the same problem.

    – zjeffer
    Jan 3 at 17:35
















3















Using a Lenovo Legion Y520 with i7-7700HQ (base clock 2.8Ghz) and GTX 1050.



I'm getting CPU overheating warnings in linux and it's affecting my performance in games (found in Payday 2 and CS:GO). I've never had problems in Windows.



This is what I found when trying to troubleshoot this issue:



In Windows 10 (using aida64)




  • Windows stays at around 3.4 Ghz on idle (no idea why this is so high with less than 3% cpu usage), with a temperature of around 50C.


  • When stressing the cpu, the temperature goes slowly from about 50C to around 75C and stays there comfortably. Clock speeds are about 2.9Ghz when stressing. Utilization is always 100%. Aida64 doesn't report throttling. The voltage on the CPU core coes from about 1.1 to 0.9 when stressing.



In Arch Linux (using s-tui)




  • Linux stays at around 2.0Ghz on idle, with a temperature of around 50C.


  • Here's where it gets weird: when stressing the cpu, the temperature IMMEDIATELY goes from 50C to about 93C. Clock speeds are exactly 3.4Ghz when stressing. Utilization is always 100%. When turing the stress test off, the temperature IMMEDIATELY goes back to about 50C, as if nothing ever happened. The laptop certainly doesn't feel like it heats up to 90C+ when doing this, even after a long stress.



Here's an image that shows how temperature, power, and frequency all go down at the exact same time. Notice how much cpu temperature changes in so little time.
Image of throttling in linux



How do I fix this throttling issue? Do I undervolt my CPU in linux? How come it reads temperatures wrong in Linux but not in Windows?



I changed the profile using cpupower from powersave to performance. I still see the same throttling in s-tui. There is a jump up in idle cpu frequency when setting to performance (instead of around 2000-2500Mhz to always at 3400Mhz), but that's the only thing that has changed.



Fan control



I tried to control fans using fancontrol (lm_sensors), but pwmconfig says there are no pwm-capable sensor modules installed.



I tried it with NBFC, but it doesn't seem to be doing anything, no matter what profile I choose. I don't even know if NBFC can control my fans, but it doesn't report any errors when choosing a profile.



I also tried thinkfan, which can control my fans, but it doesn't seem to help with throttling.



Solution



I found that lowering the maximum allowed cpu frequency using cpupower to something like 3100MHz instead of the default 3800 fixes all issues.



sudo cpupower frequency-set -u 3100MHz



I also changed max_freq in /etc/default/cpupower to the same value, to make it permanent. I found that this does result in a slight fps drop in games, but nothing serious. At least my fps is stable :)



Sadly I think this might result in decreased performance in non-gaming tasks like when compiling something.










share|improve this question




















  • 1





    Yes temperatures on microchips can jump really high almost instantaneously depending on if/how they are cooled, especially when using up lots of power. Ever touched a running CPU? I don't recommend it. Additionally, the high performance profile could still be scaling the frequency down during parts of the stress test that aren't using as much number crunching. Source: am computer engineer

    – Jeff A
    Jan 2 at 22:59













  • Thanks for the explanation. So how can I eliminate throttling when both powersave and performance don't help against throttling?

    – zjeffer
    Jan 3 at 0:05













  • If I had to take a guess, I'd say you need better cooling while you are putting high stress on the CPU/GPU. I can't really vouch for the temperature sensors and whether they actually function properly on Linux -- every motherboard is different. If you have some extra cash try getting a gaming laptop cooling pad with a bunch of fans on it. The scaling/lagging could be happening due to temperature spikes. You really want to stay below 80 degrees Celsius at all times

    – Jeff A
    Jan 3 at 0:16






  • 1





    I was thinking that maybe linux isn't turning all your fans up to the proper speed when things get hot, leading to the throttling. Have you messed around with programs that would let you control the fan speed and just put them on full blast before stress testing or gaming?

    – Jeff A
    Jan 3 at 2:55






  • 1





    I reformatted the whole post so other people can more easily find a solution if they have the same problem.

    – zjeffer
    Jan 3 at 17:35














3












3








3


1






Using a Lenovo Legion Y520 with i7-7700HQ (base clock 2.8Ghz) and GTX 1050.



I'm getting CPU overheating warnings in linux and it's affecting my performance in games (found in Payday 2 and CS:GO). I've never had problems in Windows.



This is what I found when trying to troubleshoot this issue:



In Windows 10 (using aida64)




  • Windows stays at around 3.4 Ghz on idle (no idea why this is so high with less than 3% cpu usage), with a temperature of around 50C.


  • When stressing the cpu, the temperature goes slowly from about 50C to around 75C and stays there comfortably. Clock speeds are about 2.9Ghz when stressing. Utilization is always 100%. Aida64 doesn't report throttling. The voltage on the CPU core coes from about 1.1 to 0.9 when stressing.



In Arch Linux (using s-tui)




  • Linux stays at around 2.0Ghz on idle, with a temperature of around 50C.


  • Here's where it gets weird: when stressing the cpu, the temperature IMMEDIATELY goes from 50C to about 93C. Clock speeds are exactly 3.4Ghz when stressing. Utilization is always 100%. When turing the stress test off, the temperature IMMEDIATELY goes back to about 50C, as if nothing ever happened. The laptop certainly doesn't feel like it heats up to 90C+ when doing this, even after a long stress.



Here's an image that shows how temperature, power, and frequency all go down at the exact same time. Notice how much cpu temperature changes in so little time.
Image of throttling in linux



How do I fix this throttling issue? Do I undervolt my CPU in linux? How come it reads temperatures wrong in Linux but not in Windows?



I changed the profile using cpupower from powersave to performance. I still see the same throttling in s-tui. There is a jump up in idle cpu frequency when setting to performance (instead of around 2000-2500Mhz to always at 3400Mhz), but that's the only thing that has changed.



Fan control



I tried to control fans using fancontrol (lm_sensors), but pwmconfig says there are no pwm-capable sensor modules installed.



I tried it with NBFC, but it doesn't seem to be doing anything, no matter what profile I choose. I don't even know if NBFC can control my fans, but it doesn't report any errors when choosing a profile.



I also tried thinkfan, which can control my fans, but it doesn't seem to help with throttling.



Solution



I found that lowering the maximum allowed cpu frequency using cpupower to something like 3100MHz instead of the default 3800 fixes all issues.



sudo cpupower frequency-set -u 3100MHz



I also changed max_freq in /etc/default/cpupower to the same value, to make it permanent. I found that this does result in a slight fps drop in games, but nothing serious. At least my fps is stable :)



Sadly I think this might result in decreased performance in non-gaming tasks like when compiling something.










share|improve this question
















Using a Lenovo Legion Y520 with i7-7700HQ (base clock 2.8Ghz) and GTX 1050.



I'm getting CPU overheating warnings in linux and it's affecting my performance in games (found in Payday 2 and CS:GO). I've never had problems in Windows.



This is what I found when trying to troubleshoot this issue:



In Windows 10 (using aida64)




  • Windows stays at around 3.4 Ghz on idle (no idea why this is so high with less than 3% cpu usage), with a temperature of around 50C.


  • When stressing the cpu, the temperature goes slowly from about 50C to around 75C and stays there comfortably. Clock speeds are about 2.9Ghz when stressing. Utilization is always 100%. Aida64 doesn't report throttling. The voltage on the CPU core coes from about 1.1 to 0.9 when stressing.



In Arch Linux (using s-tui)




  • Linux stays at around 2.0Ghz on idle, with a temperature of around 50C.


  • Here's where it gets weird: when stressing the cpu, the temperature IMMEDIATELY goes from 50C to about 93C. Clock speeds are exactly 3.4Ghz when stressing. Utilization is always 100%. When turing the stress test off, the temperature IMMEDIATELY goes back to about 50C, as if nothing ever happened. The laptop certainly doesn't feel like it heats up to 90C+ when doing this, even after a long stress.



Here's an image that shows how temperature, power, and frequency all go down at the exact same time. Notice how much cpu temperature changes in so little time.
Image of throttling in linux



How do I fix this throttling issue? Do I undervolt my CPU in linux? How come it reads temperatures wrong in Linux but not in Windows?



I changed the profile using cpupower from powersave to performance. I still see the same throttling in s-tui. There is a jump up in idle cpu frequency when setting to performance (instead of around 2000-2500Mhz to always at 3400Mhz), but that's the only thing that has changed.



Fan control



I tried to control fans using fancontrol (lm_sensors), but pwmconfig says there are no pwm-capable sensor modules installed.



I tried it with NBFC, but it doesn't seem to be doing anything, no matter what profile I choose. I don't even know if NBFC can control my fans, but it doesn't report any errors when choosing a profile.



I also tried thinkfan, which can control my fans, but it doesn't seem to help with throttling.



Solution



I found that lowering the maximum allowed cpu frequency using cpupower to something like 3100MHz instead of the default 3800 fixes all issues.



sudo cpupower frequency-set -u 3100MHz



I also changed max_freq in /etc/default/cpupower to the same value, to make it permanent. I found that this does result in a slight fps drop in games, but nothing serious. At least my fps is stable :)



Sadly I think this might result in decreased performance in non-gaming tasks like when compiling something.







cpu intel cpu-frequency temperature games






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 12 mins ago









Rui F Ribeiro

39.6k1479132




39.6k1479132










asked Jan 2 at 1:03









zjefferzjeffer

558




558








  • 1





    Yes temperatures on microchips can jump really high almost instantaneously depending on if/how they are cooled, especially when using up lots of power. Ever touched a running CPU? I don't recommend it. Additionally, the high performance profile could still be scaling the frequency down during parts of the stress test that aren't using as much number crunching. Source: am computer engineer

    – Jeff A
    Jan 2 at 22:59













  • Thanks for the explanation. So how can I eliminate throttling when both powersave and performance don't help against throttling?

    – zjeffer
    Jan 3 at 0:05













  • If I had to take a guess, I'd say you need better cooling while you are putting high stress on the CPU/GPU. I can't really vouch for the temperature sensors and whether they actually function properly on Linux -- every motherboard is different. If you have some extra cash try getting a gaming laptop cooling pad with a bunch of fans on it. The scaling/lagging could be happening due to temperature spikes. You really want to stay below 80 degrees Celsius at all times

    – Jeff A
    Jan 3 at 0:16






  • 1





    I was thinking that maybe linux isn't turning all your fans up to the proper speed when things get hot, leading to the throttling. Have you messed around with programs that would let you control the fan speed and just put them on full blast before stress testing or gaming?

    – Jeff A
    Jan 3 at 2:55






  • 1





    I reformatted the whole post so other people can more easily find a solution if they have the same problem.

    – zjeffer
    Jan 3 at 17:35














  • 1





    Yes temperatures on microchips can jump really high almost instantaneously depending on if/how they are cooled, especially when using up lots of power. Ever touched a running CPU? I don't recommend it. Additionally, the high performance profile could still be scaling the frequency down during parts of the stress test that aren't using as much number crunching. Source: am computer engineer

    – Jeff A
    Jan 2 at 22:59













  • Thanks for the explanation. So how can I eliminate throttling when both powersave and performance don't help against throttling?

    – zjeffer
    Jan 3 at 0:05













  • If I had to take a guess, I'd say you need better cooling while you are putting high stress on the CPU/GPU. I can't really vouch for the temperature sensors and whether they actually function properly on Linux -- every motherboard is different. If you have some extra cash try getting a gaming laptop cooling pad with a bunch of fans on it. The scaling/lagging could be happening due to temperature spikes. You really want to stay below 80 degrees Celsius at all times

    – Jeff A
    Jan 3 at 0:16






  • 1





    I was thinking that maybe linux isn't turning all your fans up to the proper speed when things get hot, leading to the throttling. Have you messed around with programs that would let you control the fan speed and just put them on full blast before stress testing or gaming?

    – Jeff A
    Jan 3 at 2:55






  • 1





    I reformatted the whole post so other people can more easily find a solution if they have the same problem.

    – zjeffer
    Jan 3 at 17:35








1




1





Yes temperatures on microchips can jump really high almost instantaneously depending on if/how they are cooled, especially when using up lots of power. Ever touched a running CPU? I don't recommend it. Additionally, the high performance profile could still be scaling the frequency down during parts of the stress test that aren't using as much number crunching. Source: am computer engineer

– Jeff A
Jan 2 at 22:59







Yes temperatures on microchips can jump really high almost instantaneously depending on if/how they are cooled, especially when using up lots of power. Ever touched a running CPU? I don't recommend it. Additionally, the high performance profile could still be scaling the frequency down during parts of the stress test that aren't using as much number crunching. Source: am computer engineer

– Jeff A
Jan 2 at 22:59















Thanks for the explanation. So how can I eliminate throttling when both powersave and performance don't help against throttling?

– zjeffer
Jan 3 at 0:05







Thanks for the explanation. So how can I eliminate throttling when both powersave and performance don't help against throttling?

– zjeffer
Jan 3 at 0:05















If I had to take a guess, I'd say you need better cooling while you are putting high stress on the CPU/GPU. I can't really vouch for the temperature sensors and whether they actually function properly on Linux -- every motherboard is different. If you have some extra cash try getting a gaming laptop cooling pad with a bunch of fans on it. The scaling/lagging could be happening due to temperature spikes. You really want to stay below 80 degrees Celsius at all times

– Jeff A
Jan 3 at 0:16





If I had to take a guess, I'd say you need better cooling while you are putting high stress on the CPU/GPU. I can't really vouch for the temperature sensors and whether they actually function properly on Linux -- every motherboard is different. If you have some extra cash try getting a gaming laptop cooling pad with a bunch of fans on it. The scaling/lagging could be happening due to temperature spikes. You really want to stay below 80 degrees Celsius at all times

– Jeff A
Jan 3 at 0:16




1




1





I was thinking that maybe linux isn't turning all your fans up to the proper speed when things get hot, leading to the throttling. Have you messed around with programs that would let you control the fan speed and just put them on full blast before stress testing or gaming?

– Jeff A
Jan 3 at 2:55





I was thinking that maybe linux isn't turning all your fans up to the proper speed when things get hot, leading to the throttling. Have you messed around with programs that would let you control the fan speed and just put them on full blast before stress testing or gaming?

– Jeff A
Jan 3 at 2:55




1




1





I reformatted the whole post so other people can more easily find a solution if they have the same problem.

– zjeffer
Jan 3 at 17:35





I reformatted the whole post so other people can more easily find a solution if they have the same problem.

– zjeffer
Jan 3 at 17:35










1 Answer
1






active

oldest

votes


















2














The difference is due to windows and linux using different CPU throttling profiles.



You do have some control over this on linux. For example, the following command will show you which profile is currently being used:



cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



There are ways to choose which profiles to use. The Arch Linux wiki has good information on this, it may be worth a read:



CPU Frequency Scaling - Arch Wiki



There is an additional issue of fan control -- you need to make sure you have the proper drivers for controllin your fans and that they are set to a high enough speed when gaming.



Linux on Laptops can be a helpful resource.






share|improve this answer





















  • 1





    Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

    – K7AAY
    Jan 2 at 18:11











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491944%2fcpu-temperatures-in-linux-throttling-or-wrong-reading%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









2














The difference is due to windows and linux using different CPU throttling profiles.



You do have some control over this on linux. For example, the following command will show you which profile is currently being used:



cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



There are ways to choose which profiles to use. The Arch Linux wiki has good information on this, it may be worth a read:



CPU Frequency Scaling - Arch Wiki



There is an additional issue of fan control -- you need to make sure you have the proper drivers for controllin your fans and that they are set to a high enough speed when gaming.



Linux on Laptops can be a helpful resource.






share|improve this answer





















  • 1





    Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

    – K7AAY
    Jan 2 at 18:11
















2














The difference is due to windows and linux using different CPU throttling profiles.



You do have some control over this on linux. For example, the following command will show you which profile is currently being used:



cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



There are ways to choose which profiles to use. The Arch Linux wiki has good information on this, it may be worth a read:



CPU Frequency Scaling - Arch Wiki



There is an additional issue of fan control -- you need to make sure you have the proper drivers for controllin your fans and that they are set to a high enough speed when gaming.



Linux on Laptops can be a helpful resource.






share|improve this answer





















  • 1





    Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

    – K7AAY
    Jan 2 at 18:11














2












2








2







The difference is due to windows and linux using different CPU throttling profiles.



You do have some control over this on linux. For example, the following command will show you which profile is currently being used:



cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



There are ways to choose which profiles to use. The Arch Linux wiki has good information on this, it may be worth a read:



CPU Frequency Scaling - Arch Wiki



There is an additional issue of fan control -- you need to make sure you have the proper drivers for controllin your fans and that they are set to a high enough speed when gaming.



Linux on Laptops can be a helpful resource.






share|improve this answer















The difference is due to windows and linux using different CPU throttling profiles.



You do have some control over this on linux. For example, the following command will show you which profile is currently being used:



cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor



There are ways to choose which profiles to use. The Arch Linux wiki has good information on this, it may be worth a read:



CPU Frequency Scaling - Arch Wiki



There is an additional issue of fan control -- you need to make sure you have the proper drivers for controllin your fans and that they are set to a high enough speed when gaming.



Linux on Laptops can be a helpful resource.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 3 at 16:36

























answered Jan 2 at 2:04









Jeff AJeff A

3316




3316








  • 1





    Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

    – K7AAY
    Jan 2 at 18:11














  • 1





    Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

    – K7AAY
    Jan 2 at 18:11








1




1





Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

– K7AAY
Jan 2 at 18:11





Jeff A, please click edit and put your findings in your original question so all may see them, then return to these comments and delete yours by clicking on the grey (X) after each. Why? Comments pile up and get hidden.

– K7AAY
Jan 2 at 18:11


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491944%2fcpu-temperatures-in-linux-throttling-or-wrong-reading%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux