kidle_inject causing very high load
Whenever kidle_inject
starts running on my system the load shoots up. In general it only gets to a load of around this 5.23, 3.65, 2.54
but a lot of the time it jumps up past the 15 mark on each of them. At that point the system grinds to a halt and I have to power it off.
This only happens when the kidle_inject
process starts. How can I disable this process so my machine can work and I can get some work done.
Example top
:
top - 12:43:48 up 3:02, 3 users, load average: 6.57, 5.53, 3.33
Tasks: 256 total, 3 running, 253 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.9 us, 16.6 sy, 0.0 ni, 74.7 id, 0.5 wa, 0.0 hi, 2.3 si, 0.0 st
KiB Mem: 8080252 total, 7937856 used, 142396 free, 258904 buffers
KiB Swap: 0 total, 0 used, 0 free. 4061336 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
13509 root -51 0 0 0 0 S 54.7 0.0 3:29.47 kidle_inject/1
13511 root -51 0 0 0 0 S 54.1 0.0 3:30.92 kidle_inject/3
13510 root -51 0 0 0 0 S 48.8 0.0 3:11.60 kidle_inject/2
13508 root -51 0 0 0 0 S 47.6 0.0 3:08.47 kidle_inject/0
14.10 intel
add a comment |
Whenever kidle_inject
starts running on my system the load shoots up. In general it only gets to a load of around this 5.23, 3.65, 2.54
but a lot of the time it jumps up past the 15 mark on each of them. At that point the system grinds to a halt and I have to power it off.
This only happens when the kidle_inject
process starts. How can I disable this process so my machine can work and I can get some work done.
Example top
:
top - 12:43:48 up 3:02, 3 users, load average: 6.57, 5.53, 3.33
Tasks: 256 total, 3 running, 253 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.9 us, 16.6 sy, 0.0 ni, 74.7 id, 0.5 wa, 0.0 hi, 2.3 si, 0.0 st
KiB Mem: 8080252 total, 7937856 used, 142396 free, 258904 buffers
KiB Swap: 0 total, 0 used, 0 free. 4061336 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
13509 root -51 0 0 0 0 S 54.7 0.0 3:29.47 kidle_inject/1
13511 root -51 0 0 0 0 S 54.1 0.0 3:30.92 kidle_inject/3
13510 root -51 0 0 0 0 S 48.8 0.0 3:11.60 kidle_inject/2
13508 root -51 0 0 0 0 S 47.6 0.0 3:08.47 kidle_inject/0
14.10 intel
add a comment |
Whenever kidle_inject
starts running on my system the load shoots up. In general it only gets to a load of around this 5.23, 3.65, 2.54
but a lot of the time it jumps up past the 15 mark on each of them. At that point the system grinds to a halt and I have to power it off.
This only happens when the kidle_inject
process starts. How can I disable this process so my machine can work and I can get some work done.
Example top
:
top - 12:43:48 up 3:02, 3 users, load average: 6.57, 5.53, 3.33
Tasks: 256 total, 3 running, 253 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.9 us, 16.6 sy, 0.0 ni, 74.7 id, 0.5 wa, 0.0 hi, 2.3 si, 0.0 st
KiB Mem: 8080252 total, 7937856 used, 142396 free, 258904 buffers
KiB Swap: 0 total, 0 used, 0 free. 4061336 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
13509 root -51 0 0 0 0 S 54.7 0.0 3:29.47 kidle_inject/1
13511 root -51 0 0 0 0 S 54.1 0.0 3:30.92 kidle_inject/3
13510 root -51 0 0 0 0 S 48.8 0.0 3:11.60 kidle_inject/2
13508 root -51 0 0 0 0 S 47.6 0.0 3:08.47 kidle_inject/0
14.10 intel
Whenever kidle_inject
starts running on my system the load shoots up. In general it only gets to a load of around this 5.23, 3.65, 2.54
but a lot of the time it jumps up past the 15 mark on each of them. At that point the system grinds to a halt and I have to power it off.
This only happens when the kidle_inject
process starts. How can I disable this process so my machine can work and I can get some work done.
Example top
:
top - 12:43:48 up 3:02, 3 users, load average: 6.57, 5.53, 3.33
Tasks: 256 total, 3 running, 253 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.9 us, 16.6 sy, 0.0 ni, 74.7 id, 0.5 wa, 0.0 hi, 2.3 si, 0.0 st
KiB Mem: 8080252 total, 7937856 used, 142396 free, 258904 buffers
KiB Swap: 0 total, 0 used, 0 free. 4061336 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
13509 root -51 0 0 0 0 S 54.7 0.0 3:29.47 kidle_inject/1
13511 root -51 0 0 0 0 S 54.1 0.0 3:30.92 kidle_inject/3
13510 root -51 0 0 0 0 S 48.8 0.0 3:11.60 kidle_inject/2
13508 root -51 0 0 0 0 S 47.6 0.0 3:08.47 kidle_inject/0
14.10 intel
14.10 intel
edited Apr 8 '17 at 0:23
Carolus
181113
181113
asked Feb 12 '15 at 12:24
NalumNalum
87811014
87811014
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
It appears that this is a bug in the kernel.
From the comments on that bug report, running the command sudo rmmod intel_powerclamp
seems to have stopped the kidle_inject
processes and I haven't noticed any issues with doing so as of yet.
Hopefully this will be fixed soon. If I do notice anything I will update this answer.
Update
The rmmod
command needs to be run every time you boot the machine. I have not noticed anything bad happening since running this command.
Update 2
I have noticed since doing this that my CPU temp now tends to run much lower at around the ~72°
For making this set while booting use a command
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
18
You don't have to run that command every time you boot. You can just blacklist it withecho "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
3
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?
– cat
May 4 '16 at 23:34
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
1
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
|
show 6 more comments
The accepted answer is incomplete. According to the bug comments, the kidle_inject processes are spawned to throttle processor and protect it from further overheating.
Before "fixing" the bug, make sure your fan is clean and works correctly. I had this problem and found out that the vent was full of dust. After cleaning and reboot no kidle_inject was spawned anymore.
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
1
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
1
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
add a comment |
If you are running a macbook, make sure that you have macfanctld
installed. If you don't, the fan will be fixed at around 2000 RPM out of the max 6000. This can be seen by the sensors
command. In this situation powerclamp will kick in to save the CPUs rather early.
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
add a comment |
I noticed this today as well. Oddly enough for the kind of CPU usage, the fan wasn't making any noise. Managed to reboot the machine and then looked at BIOS Fan speed. It showed that the fan had stopped (no RPM reading). So after a bit of a cleaning (quite literally - opening the laptop lid, cleaning a bit, the fan started working fine and things got alright. So might be the problem is with your CPU fan. So simply disabling the intel_powerclamp
may not be a good idea.
add a comment |
I did the following and it works perfectly :
1. check if the module is loaded: lsmod |grep -i intel_powerclamp
2. if previous command show that module is loaded, perform the next lines.
3.add the following line in your crontab rules "@reboot /sbin/rmmod intel_powerclamp" or "echo '/sbin/rmmod intel_powerclamp' >> /etc/bash.bashrc" (it will affect to all users) or "echo 'blacklist intel_powerclamp' > /etc/modprobe.d/disable_mods.conf".
best regards,
New contributor
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%2f584636%2fkidle-inject-causing-very-high-load%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
It appears that this is a bug in the kernel.
From the comments on that bug report, running the command sudo rmmod intel_powerclamp
seems to have stopped the kidle_inject
processes and I haven't noticed any issues with doing so as of yet.
Hopefully this will be fixed soon. If I do notice anything I will update this answer.
Update
The rmmod
command needs to be run every time you boot the machine. I have not noticed anything bad happening since running this command.
Update 2
I have noticed since doing this that my CPU temp now tends to run much lower at around the ~72°
For making this set while booting use a command
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
18
You don't have to run that command every time you boot. You can just blacklist it withecho "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
3
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?
– cat
May 4 '16 at 23:34
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
1
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
|
show 6 more comments
It appears that this is a bug in the kernel.
From the comments on that bug report, running the command sudo rmmod intel_powerclamp
seems to have stopped the kidle_inject
processes and I haven't noticed any issues with doing so as of yet.
Hopefully this will be fixed soon. If I do notice anything I will update this answer.
Update
The rmmod
command needs to be run every time you boot the machine. I have not noticed anything bad happening since running this command.
Update 2
I have noticed since doing this that my CPU temp now tends to run much lower at around the ~72°
For making this set while booting use a command
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
18
You don't have to run that command every time you boot. You can just blacklist it withecho "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
3
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?
– cat
May 4 '16 at 23:34
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
1
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
|
show 6 more comments
It appears that this is a bug in the kernel.
From the comments on that bug report, running the command sudo rmmod intel_powerclamp
seems to have stopped the kidle_inject
processes and I haven't noticed any issues with doing so as of yet.
Hopefully this will be fixed soon. If I do notice anything I will update this answer.
Update
The rmmod
command needs to be run every time you boot the machine. I have not noticed anything bad happening since running this command.
Update 2
I have noticed since doing this that my CPU temp now tends to run much lower at around the ~72°
For making this set while booting use a command
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
It appears that this is a bug in the kernel.
From the comments on that bug report, running the command sudo rmmod intel_powerclamp
seems to have stopped the kidle_inject
processes and I haven't noticed any issues with doing so as of yet.
Hopefully this will be fixed soon. If I do notice anything I will update this answer.
Update
The rmmod
command needs to be run every time you boot the machine. I have not noticed anything bad happening since running this command.
Update 2
I have noticed since doing this that my CPU temp now tends to run much lower at around the ~72°
For making this set while booting use a command
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
edited Sep 19 '16 at 11:28
podarok
1195
1195
answered Feb 16 '15 at 11:20
NalumNalum
87811014
87811014
18
You don't have to run that command every time you boot. You can just blacklist it withecho "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
3
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?
– cat
May 4 '16 at 23:34
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
1
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
|
show 6 more comments
18
You don't have to run that command every time you boot. You can just blacklist it withecho "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
3
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?
– cat
May 4 '16 at 23:34
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
1
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
18
18
You don't have to run that command every time you boot. You can just blacklist it with
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
You don't have to run that command every time you boot. You can just blacklist it with
echo "blacklist intel_powerclamp" > /etc/modprobe.d/disable-powerclamp.conf
– Jesse
Mar 15 '15 at 23:06
3
3
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?– cat
May 4 '16 at 23:34
Hopefully this will be fixed soon
Yeah, hopefully... come on, it's 2016, I think we're on kernel version 87 now? can we please move past the "haha lets overheat the computer for shits and giggles" thing?– cat
May 4 '16 at 23:34
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
Love you man! You saved my ass today
– Abhishek Gupta
Jun 6 '16 at 11:47
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
This is not actually a bug, but a feature to prevent the processor from further overheating. I'd also suggest reading this.
– user364819
Nov 20 '16 at 18:02
1
1
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
Instant improvement for me, Thank You. Running Kubuntu 18.04 on a clevo laptop. kernel 4.15.0-20.
– kshepherd
May 4 '18 at 14:35
|
show 6 more comments
The accepted answer is incomplete. According to the bug comments, the kidle_inject processes are spawned to throttle processor and protect it from further overheating.
Before "fixing" the bug, make sure your fan is clean and works correctly. I had this problem and found out that the vent was full of dust. After cleaning and reboot no kidle_inject was spawned anymore.
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
1
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
1
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
add a comment |
The accepted answer is incomplete. According to the bug comments, the kidle_inject processes are spawned to throttle processor and protect it from further overheating.
Before "fixing" the bug, make sure your fan is clean and works correctly. I had this problem and found out that the vent was full of dust. After cleaning and reboot no kidle_inject was spawned anymore.
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
1
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
1
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
add a comment |
The accepted answer is incomplete. According to the bug comments, the kidle_inject processes are spawned to throttle processor and protect it from further overheating.
Before "fixing" the bug, make sure your fan is clean and works correctly. I had this problem and found out that the vent was full of dust. After cleaning and reboot no kidle_inject was spawned anymore.
The accepted answer is incomplete. According to the bug comments, the kidle_inject processes are spawned to throttle processor and protect it from further overheating.
Before "fixing" the bug, make sure your fan is clean and works correctly. I had this problem and found out that the vent was full of dust. After cleaning and reboot no kidle_inject was spawned anymore.
answered Jun 16 '16 at 12:52
johnnyjohnny
32122
32122
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
1
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
1
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
add a comment |
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
1
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
1
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
Thank you for adding this note. I will also note that this was happening to my machine which was brand new. I have since setup debian on it and have had no issues and no need to apply this temporary fix.
– Nalum
Jun 16 '16 at 12:55
1
1
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
the expected aim of that process may very well be to protect the cpu from overheating, but how can it do that while taking 50% or more of the cpu load? that's the bug. I had to stop that process too, and replaced it when necessary with a cpu-throttle script
– user47206
Apr 3 '17 at 17:45
1
1
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
Good point, you're right that it doesn't directly protect the CPU. Maybe it will raise the user's attention though, since he will find that the computer is unusable and will do something about it. It would indeed be a better solution to underclock the CPU and notify user about its high temperatures.
– johnny
Dec 15 '17 at 18:13
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
I'm having this issue when the chip is downright cold. Clean fan (brand-new fan), frigid operating environment (have been concerned I might need to insulate it to protect other components, like the battery, but so far, system's not dropped cold enough to need it), and the system is still cripplingly slow, with these running on it.
– Matthew Najmon
Jan 27 at 14:30
add a comment |
If you are running a macbook, make sure that you have macfanctld
installed. If you don't, the fan will be fixed at around 2000 RPM out of the max 6000. This can be seen by the sensors
command. In this situation powerclamp will kick in to save the CPUs rather early.
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
add a comment |
If you are running a macbook, make sure that you have macfanctld
installed. If you don't, the fan will be fixed at around 2000 RPM out of the max 6000. This can be seen by the sensors
command. In this situation powerclamp will kick in to save the CPUs rather early.
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
add a comment |
If you are running a macbook, make sure that you have macfanctld
installed. If you don't, the fan will be fixed at around 2000 RPM out of the max 6000. This can be seen by the sensors
command. In this situation powerclamp will kick in to save the CPUs rather early.
If you are running a macbook, make sure that you have macfanctld
installed. If you don't, the fan will be fixed at around 2000 RPM out of the max 6000. This can be seen by the sensors
command. In this situation powerclamp will kick in to save the CPUs rather early.
edited Apr 20 '17 at 12:09
answered Apr 4 '17 at 21:36
Alexander TorstlingAlexander Torstling
23123
23123
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
add a comment |
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
I would argue that the answer is not complete without this being included.
– theYnot
Jun 6 '17 at 10:16
add a comment |
I noticed this today as well. Oddly enough for the kind of CPU usage, the fan wasn't making any noise. Managed to reboot the machine and then looked at BIOS Fan speed. It showed that the fan had stopped (no RPM reading). So after a bit of a cleaning (quite literally - opening the laptop lid, cleaning a bit, the fan started working fine and things got alright. So might be the problem is with your CPU fan. So simply disabling the intel_powerclamp
may not be a good idea.
add a comment |
I noticed this today as well. Oddly enough for the kind of CPU usage, the fan wasn't making any noise. Managed to reboot the machine and then looked at BIOS Fan speed. It showed that the fan had stopped (no RPM reading). So after a bit of a cleaning (quite literally - opening the laptop lid, cleaning a bit, the fan started working fine and things got alright. So might be the problem is with your CPU fan. So simply disabling the intel_powerclamp
may not be a good idea.
add a comment |
I noticed this today as well. Oddly enough for the kind of CPU usage, the fan wasn't making any noise. Managed to reboot the machine and then looked at BIOS Fan speed. It showed that the fan had stopped (no RPM reading). So after a bit of a cleaning (quite literally - opening the laptop lid, cleaning a bit, the fan started working fine and things got alright. So might be the problem is with your CPU fan. So simply disabling the intel_powerclamp
may not be a good idea.
I noticed this today as well. Oddly enough for the kind of CPU usage, the fan wasn't making any noise. Managed to reboot the machine and then looked at BIOS Fan speed. It showed that the fan had stopped (no RPM reading). So after a bit of a cleaning (quite literally - opening the laptop lid, cleaning a bit, the fan started working fine and things got alright. So might be the problem is with your CPU fan. So simply disabling the intel_powerclamp
may not be a good idea.
answered Jan 8 at 12:45
gabhijitgabhijit
101
101
add a comment |
add a comment |
I did the following and it works perfectly :
1. check if the module is loaded: lsmod |grep -i intel_powerclamp
2. if previous command show that module is loaded, perform the next lines.
3.add the following line in your crontab rules "@reboot /sbin/rmmod intel_powerclamp" or "echo '/sbin/rmmod intel_powerclamp' >> /etc/bash.bashrc" (it will affect to all users) or "echo 'blacklist intel_powerclamp' > /etc/modprobe.d/disable_mods.conf".
best regards,
New contributor
add a comment |
I did the following and it works perfectly :
1. check if the module is loaded: lsmod |grep -i intel_powerclamp
2. if previous command show that module is loaded, perform the next lines.
3.add the following line in your crontab rules "@reboot /sbin/rmmod intel_powerclamp" or "echo '/sbin/rmmod intel_powerclamp' >> /etc/bash.bashrc" (it will affect to all users) or "echo 'blacklist intel_powerclamp' > /etc/modprobe.d/disable_mods.conf".
best regards,
New contributor
add a comment |
I did the following and it works perfectly :
1. check if the module is loaded: lsmod |grep -i intel_powerclamp
2. if previous command show that module is loaded, perform the next lines.
3.add the following line in your crontab rules "@reboot /sbin/rmmod intel_powerclamp" or "echo '/sbin/rmmod intel_powerclamp' >> /etc/bash.bashrc" (it will affect to all users) or "echo 'blacklist intel_powerclamp' > /etc/modprobe.d/disable_mods.conf".
best regards,
New contributor
I did the following and it works perfectly :
1. check if the module is loaded: lsmod |grep -i intel_powerclamp
2. if previous command show that module is loaded, perform the next lines.
3.add the following line in your crontab rules "@reboot /sbin/rmmod intel_powerclamp" or "echo '/sbin/rmmod intel_powerclamp' >> /etc/bash.bashrc" (it will affect to all users) or "echo 'blacklist intel_powerclamp' > /etc/modprobe.d/disable_mods.conf".
best regards,
New contributor
New contributor
answered 5 mins ago
Manuel LazoManuel Lazo
1
1
New contributor
New contributor
add a comment |
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.
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%2f584636%2fkidle-inject-causing-very-high-load%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