You are correct that the CPU use is in the 3-5% range, that in itself isn't the problem. The problem is that it is ALWAYS 3-5% and ALWAYS at the top of the list. That signifies a runaway process in tdepowersave that is not playing nicely. tdepowersave should only require 3-5% of the cpu when it does something, not continually. tdepowersave should only be monitoring input and starting timers, screensavers, suspend, etc.... Those are all negligible and darn sure less that was X is doing. So there is a live Gremlin in tdepowersave somewhere....
Yes, I understood that ALWAYS 3% is an unhealthy indication. That was what I was implying when I shared that kmix and knotification- daemon were always at about 2%.
I don't know whether Slavek's patch will remedy the ALWAYS problem, but we should look at all three apps for why they are consistently at the top of top.
Darrell
On 02/01/2014 01:13 PM, Darrell Anderson wrote:
Yes, I understood that ALWAYS 3% is an unhealthy indication. That was what I was implying when I shared that kmix and knotification- daemon were always at about 2%.
I don't know whether Slavek's patch will remedy the ALWAYS problem, but we should look at all three apps for why they are consistently at the top of top.
Darrell
The only thing that looks out of place is 'tdepowersave' in top. Of course kmix is dead for me, but everything else look OK.
On 02/01/2014 01:55 PM, David C. Rankin wrote:
On 02/01/2014 01:13 PM, Darrell Anderson wrote:
Yes, I understood that ALWAYS 3% is an unhealthy indication. That was what I was implying when I shared that kmix and knotification- daemon were always at about 2%.
I don't know whether Slavek's patch will remedy the ALWAYS problem, but we should look at all three apps for why they are consistently at the top of top.
Darrell
The only thing that looks out of place is 'tdepowersave' in top. Of course kmix is dead for me, but everything else look OK.
When on the old 3.5.13-sru install, I checked top. No problem with kpowersave there. The only issue there was artsd eating 10-12% CPU.
Am Samstag, 1. Februar 2014 schrieb David C. Rankin:
On 02/01/2014 01:55 PM, David C. Rankin wrote:
On 02/01/2014 01:13 PM, Darrell Anderson wrote:
Yes, I understood that ALWAYS 3% is an unhealthy indication. That was what I was implying when I shared that kmix and knotification- daemon were always at about 2%.
I don't know whether Slavek's patch will remedy the ALWAYS problem, but we should look at all three apps for why they are consistently at the top of top.
Darrell
The only thing that looks out of place is 'tdepowersave' in top. Of course kmix is dead for me, but everything else look OK.
When on the old 3.5.13-sru install, I checked top. No problem with kpowersave there. The only issue there was artsd eating 10-12% CPU.
Interesting. I have 3.5.13.2on my X61. When I disconnect the power line, then kpowersave eats 100% of one core. Funny thing is, this does not happen all the time. I have a script, that restarts kpowersave when it consumes more than 50% cpu :-)
Nik
On 02/01/2014 02:36 PM, Dr. Nikolaus Klepp wrote:
Interesting. I have 3.5.13.2on my X61. When I disconnect the power line, then kpowersave eats 100% of one core. Funny thing is, this does not happen all the time. I have a script, that restarts kpowersave when it consumes more than 50% cpu :-)
Nik
That would be an interesting test. I run most test installs in vitrualbox, so pulling the plug isn't an option. I have 3.5.13-sru-1 installed on a desktop, but pulling power there......
I have suse's 3.5 on a laptop and there are no kpowersave issues. We should check with Ilya or Robert and see what they are doing to kpowersave. I'm on the kde3 list there. I'll ask.
-
Darrell Anderson -
David C. Rankin -
Dr. Nikolaus Klepp