| 2016-07-10 12:51:54 |
teo1978 |
bug |
|
|
added bug |
| 2016-07-10 12:54:42 |
teo1978 |
description |
** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all.
I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration.
This is on a laptop, which has an actual physical cooling fan (like most laptops).
EXPECTED BEHAVIOR:
as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when things like intel powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight.
On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you note the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown)
OBSERVED BEHAVIOR
When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of.
To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive.
Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl.
So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that in needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon.
It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust and uncapable of doing its job efficiently (which is also true but is not the whole story).
Until I realised that when I was observing unresponsiveness, the fan was not even close to its maximum speed.
CONCLUSION: either thermald does a ridiculously bad job, or its default configuration is ridiculously bad.
NOTE: this issue is **CRITICAL**: this cripples the whole system making it unresponsive when doing moderately heavy work (which the system would otherwise be perfectly capable of handling without overheating).
Most non-geek users don't even know what thermald is and will never find out that they can work around the problem by shutting it down, let alone fix its configuration. So, for most users, this "renders the system temporarily or permanently unusable", which is one of the criteria for critical importance.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: thermald 1.4.3-5ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 14:03:56 2016
InstallationDate: Installed on 2013-10-11 (1002 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: thermald
UpgradeStatus: Upgraded to wily on 2016-01-18 (174 days ago) |
** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all.
I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration.
This is on a laptop, which has an actual physical cooling fan (like most laptops).
EXPECTED BEHAVIOR:
as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight.
On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you note the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown)
OBSERVED BEHAVIOR
When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of.
To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive.
Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl.
So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that in needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon.
It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust and uncapable of doing its job efficiently (which is also true but is not the whole story).
Until I realised that when I was observing unresponsiveness, the fan was not even close to its maximum speed.
CONCLUSION: either thermald does a ridiculously bad job, or its default configuration is ridiculously bad.
NOTE: this issue is **CRITICAL**: this cripples the whole system making it unresponsive when doing moderately heavy work (which the system would otherwise be perfectly capable of handling without overheating).
Most non-geek users don't even know what thermald is and will never find out that they can work around the problem by shutting it down, let alone fix its configuration. So, for most users, this "renders the system temporarily or permanently unusable", which is one of the criteria for critical importance.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: thermald 1.4.3-5ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 14:03:56 2016
InstallationDate: Installed on 2013-10-11 (1002 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: thermald
UpgradeStatus: Upgraded to wily on 2016-01-18 (174 days ago) |
|
| 2016-07-10 12:56:13 |
teo1978 |
description |
** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all.
I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration.
This is on a laptop, which has an actual physical cooling fan (like most laptops).
EXPECTED BEHAVIOR:
as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight.
On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you note the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown)
OBSERVED BEHAVIOR
When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of.
To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive.
Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl.
So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that in needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon.
It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust and uncapable of doing its job efficiently (which is also true but is not the whole story).
Until I realised that when I was observing unresponsiveness, the fan was not even close to its maximum speed.
CONCLUSION: either thermald does a ridiculously bad job, or its default configuration is ridiculously bad.
NOTE: this issue is **CRITICAL**: this cripples the whole system making it unresponsive when doing moderately heavy work (which the system would otherwise be perfectly capable of handling without overheating).
Most non-geek users don't even know what thermald is and will never find out that they can work around the problem by shutting it down, let alone fix its configuration. So, for most users, this "renders the system temporarily or permanently unusable", which is one of the criteria for critical importance.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: thermald 1.4.3-5ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 14:03:56 2016
InstallationDate: Installed on 2013-10-11 (1002 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: thermald
UpgradeStatus: Upgraded to wily on 2016-01-18 (174 days ago) |
** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all.
I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration.
This is on a laptop, which has an actual physical cooling fan (like most laptops).
EXPECTED BEHAVIOR:
as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight.
On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you notice the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown)
OBSERVED BEHAVIOR
When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of.
To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive.
Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl.
So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that in needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon.
It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust and uncapable of doing its job efficiently (which is also true but is not the whole story).
Until I realised that when I was observing unresponsiveness, the fan was not even close to its maximum speed.
CONCLUSION: either thermald does a ridiculously bad job, or its default configuration is ridiculously bad.
NOTE: this issue is **CRITICAL**: this cripples the whole system making it unresponsive when doing moderately heavy work (which the system would otherwise be perfectly capable of handling without overheating).
Most non-geek users don't even know what thermald is and will never find out that they can work around the problem by shutting it down, let alone fix its configuration. So, for most users, this "renders the system temporarily or permanently unusable", which is one of the criteria for critical importance.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: thermald 1.4.3-5ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 14:03:56 2016
InstallationDate: Installed on 2013-10-11 (1002 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: thermald
UpgradeStatus: Upgraded to wily on 2016-01-18 (174 days ago) |
|
| 2016-07-10 12:57:51 |
teo1978 |
description |
** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all.
I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration.
This is on a laptop, which has an actual physical cooling fan (like most laptops).
EXPECTED BEHAVIOR:
as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight.
On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you notice the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown)
OBSERVED BEHAVIOR
When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of.
To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive.
Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl.
So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that in needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon.
It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust and uncapable of doing its job efficiently (which is also true but is not the whole story).
Until I realised that when I was observing unresponsiveness, the fan was not even close to its maximum speed.
CONCLUSION: either thermald does a ridiculously bad job, or its default configuration is ridiculously bad.
NOTE: this issue is **CRITICAL**: this cripples the whole system making it unresponsive when doing moderately heavy work (which the system would otherwise be perfectly capable of handling without overheating).
Most non-geek users don't even know what thermald is and will never find out that they can work around the problem by shutting it down, let alone fix its configuration. So, for most users, this "renders the system temporarily or permanently unusable", which is one of the criteria for critical importance.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: thermald 1.4.3-5ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 14:03:56 2016
InstallationDate: Installed on 2013-10-11 (1002 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: thermald
UpgradeStatus: Upgraded to wily on 2016-01-18 (174 days ago) |
** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all.
I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration.
This is on a laptop, which has an actual physical cooling fan (like most laptops).
EXPECTED BEHAVIOR:
as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight.
On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you notice the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown)
OBSERVED BEHAVIOR
When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of.
To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive.
Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl.
So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that it needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon.
It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust and uncapable of doing its job efficiently (which is also true but is not the whole story).
Until I realised that when I was observing unresponsiveness, the fan was not even close to its maximum speed.
CONCLUSION: either thermald does a ridiculously bad job, or its default configuration is ridiculously bad.
NOTE: this issue is **CRITICAL**: this cripples the whole system making it unresponsive when doing moderately heavy work (which the system would otherwise be perfectly capable of handling without overheating).
Most non-geek users don't even know what thermald is and will never find out that they can work around the problem by shutting it down, let alone fix its configuration. So, for most users, this "renders the system temporarily or permanently unusable", which is one of the criteria for critical importance.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: thermald 1.4.3-5ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 14:03:56 2016
InstallationDate: Installed on 2013-10-11 (1002 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: thermald
UpgradeStatus: Upgraded to wily on 2016-01-18 (174 days ago) |
|
| 2016-07-10 13:41:52 |
dino99 |
thermald (Ubuntu): status |
New |
Invalid |
|
| 2016-07-10 15:04:49 |
teo1978 |
thermald (Ubuntu): status |
Invalid |
New |
|
| 2016-07-10 15:32:15 |
dino99 |
thermald (Ubuntu): status |
New |
Invalid |
|
| 2017-01-23 00:31:30 |
Kwang Moo Yi |
bug |
|
|
added subscriber Kwang Moo Yi |
| 2017-01-23 00:33:26 |
Kwang Moo Yi |
tags |
amd64 apport-bug wily |
amd64 apport-bug wily xenial |
|
| 2017-02-01 20:20:10 |
Kasper Peeters |
bug |
|
|
added subscriber Kasper Peeters |
| 2017-02-08 19:38:57 |
teo1978 |
thermald (Ubuntu): status |
Invalid |
Confirmed |
|
| 2017-02-09 01:14:02 |
mike@papersolve.com |
bug |
|
|
added subscriber mike@papersolve.com |
| 2017-02-09 01:54:35 |
Doug Smythies |
bug |
|
|
added subscriber Doug Smythies |
| 2017-02-09 01:57:17 |
mike@papersolve.com |
attachment added |
|
thermald debug logs which ends up with thermald stuck in a low freq mode when CPU is cool https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1600599/+attachment/4815661/+files/thermald-debug-reduced.log |
|
| 2017-02-09 14:46:49 |
mike@papersolve.com |
attachment added |
|
thermald debug log 2 https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1600599/+attachment/4815852/+files/thermald-debug-2017-02-09.log |
|
| 2017-02-09 15:35:26 |
mike@papersolve.com |
attachment added |
|
thermald log where starting it puts me back to max performance https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1600599/+attachment/4815896/+files/thermald-debug-2017-02-09_2.log |
|
| 2017-02-10 16:24:44 |
Alberto Salvia Novella |
thermald (Ubuntu): importance |
Undecided |
Critical |
|
| 2017-02-10 17:41:59 |
mike@papersolve.com |
attachment added |
|
logs.zip https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1600599/+attachment/4816650/+files/logs.zip |
|
| 2017-02-11 06:59:45 |
Launchpad Janitor |
thermald (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2017-12-18 03:47:59 |
Chen-Han Hsiao (Stanley) |
bug |
|
|
added subscriber Chen-Han Hsiao (Stanley) |
| 2019-08-15 17:19:31 |
Andy Whitcroft |
thermald (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-08-15 17:19:34 |
Andy Whitcroft |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-08-15 17:19:37 |
Andy Whitcroft |
bug |
|
|
added subscriber SRU Verification |
| 2019-08-15 17:19:43 |
Andy Whitcroft |
tags |
amd64 apport-bug wily xenial |
amd64 apport-bug verification-needed verification-needed-bionic wily xenial |
|
| 2019-08-15 17:44:47 |
Colin Ian King |
bug task deleted |
thermald (Ubuntu Bionic) |
|
|
| 2019-08-15 17:47:30 |
Colin Ian King |
tags |
amd64 apport-bug verification-needed verification-needed-bionic wily xenial |
amd64 apport-bug verification-done wily xenial |
|
