Darrell, Slavek, All,
On your R14 install, open a 'top' or 'htop' window and tell me what your 'tdepowersave' use is.
By far -- tdepowersave is the top CPU user on my build continually taking more than any other process. This is not right. It is using 2x-3x more CPU than X or kded and is continually at the top of the list. It never stops.
What do you see?
On Saturday 01 of February 2014 19:04:56 David C. Rankin wrote:
Darrell, Slavek, All,
On your R14 install, open a 'top' or 'htop' window and tell me what your 'tdepowersave' use is.
By far -- tdepowersave is the top CPU user on my build continually taking more than any other process. This is not right. It is using 2x-3x more CPU than X or kded and is continually at the top of the list. It never stops.
What do you see?
Soon I will have completed a patch for tdepowersave (related to bug 1597). Let's wait with further research after this patch.
Slavek --
On 02/01/2014 12:13 PM, Slávek Banko wrote:
On Saturday 01 of February 2014 19:04:56 David C. Rankin wrote:
Darrell, Slavek, All,
On your R14 install, open a 'top' or 'htop' window and tell me what your 'tdepowersave' use is.
By far -- tdepowersave is the top CPU user on my build continually taking more than any other process. This is not right. It is using 2x-3x more CPU than X or kded and is continually at the top of the list. It never stops.
What do you see?
Soon I will have completed a patch for tdepowersave (related to bug 1597). Let's wait with further research after this patch.
Slavek
Ok,
Is there any suggestion for managing tdepowersave CPU use in the interim? If I have it running in virtualbox on my laptop, then my palmrest gets fairly warm ;-)
On Saturday 01 of February 2014 19:24:39 David C. Rankin wrote:
On 02/01/2014 12:13 PM, Slávek Banko wrote:
On Saturday 01 of February 2014 19:04:56 David C. Rankin wrote:
Darrell, Slavek, All,
On your R14 install, open a 'top' or 'htop' window and tell me what your 'tdepowersave' use is.
By far -- tdepowersave is the top CPU user on my build continually taking more than any other process. This is not right. It is using 2x-3x more CPU than X or kded and is continually at the top of the list. It never stops.
What do you see?
Soon I will have completed a patch for tdepowersave (related to bug 1597). Let's wait with further research after this patch.
Slavek
Ok,
Is there any suggestion for managing tdepowersave CPU use in the interim? If I have it running in virtualbox on my laptop, then my palmrest gets fairly warm ;-)
I have tdepowersave on the two test virtual machines in KVM (first Debian 7.3 - Wheezy, second Ubuntu 13.10 - Saucy) and tdepowersave (with a patch, which I'm finishing) I have constantly at 0% CPU. On the real machine (with battery) I have not tested it yet.
Slavek --
On 02/01/2014 12:39 PM, Slávek Banko wrote:
I have tdepowersave on the two test virtual machines in KVM (first Debian 7.3 - Wheezy, second Ubuntu 13.10 - Saucy) and tdepowersave (with a patch, which I'm finishing) I have constantly at 0% CPU. On the real machine (with battery) I have not tested it yet.
Share the patch and I will help test :-)
On Saturday 01 of February 2014 19:45:35 David C. Rankin wrote:
On 02/01/2014 12:39 PM, Slávek Banko wrote:
I have tdepowersave on the two test virtual machines in KVM (first Debian 7.3 - Wheezy, second Ubuntu 13.10 - Saucy) and tdepowersave (with a patch, which I'm finishing) I have constantly at 0% CPU. On the real machine (with battery) I have not tested it yet.
Share the patch and I will help test :-)
Late yesterday night I was finishing the last part. Now is a patch attached to the bug report 1597 - attachment 1910.
Please try it. I'll wait with pushing patch to GIT.
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1597 http://bugs.pearsoncomputing.net/attachment.cgi?id=1910
On 02/02/2014 09:50 AM, Slávek Banko wrote:
Late yesterday night I was finishing the last part. Now is a patch attached to the bug report 1597 - attachment 1910.
Please try it. I'll wait with pushing patch to GIT.
OK, will report back
On 02/02/2014 11:12 AM, David C. Rankin wrote:
On 02/02/2014 09:50 AM, Slávek Banko wrote:
Late yesterday night I was finishing the last part. Now is a patch attached to the bug report 1597 - attachment 1910.
Please try it. I'll wait with pushing patch to GIT.
OK, will report back
Reporting back - tdepowersave CRASHED BIGTIME on start. I'll have to rebuild with full debug. I had not symbols in package.
DON'T PUSH -- SOMETHING NOT RIGHT
It builds fine, but craters on start.
On Sunday 02 of February 2014 19:47:28 David C. Rankin wrote:
On 02/02/2014 11:12 AM, David C. Rankin wrote:
On 02/02/2014 09:50 AM, Slávek Banko wrote:
Late yesterday night I was finishing the last part. Now is a patch attached to the bug report 1597 - attachment 1910.
Please try it. I'll wait with pushing patch to GIT.
OK, will report back
Reporting back - tdepowersave CRASHED BIGTIME on start. I'll have to rebuild with full debug. I had not symbols in package.
DON'T PUSH -- SOMETHING NOT RIGHT
It builds fine, but craters on start.
You have updated dbus-1-tqt? See comment in bug 1597.
On 02/02/2014 01:13 PM, Slávek Banko wrote:
On Sunday 02 of February 2014 19:47:28 David C. Rankin wrote:
On 02/02/2014 11:12 AM, David C. Rankin wrote:
On 02/02/2014 09:50 AM, Slávek Banko wrote:
Late yesterday night I was finishing the last part. Now is a patch attached to the bug report 1597 - attachment 1910.
Please try it. I'll wait with pushing patch to GIT.
OK, will report back
Reporting back - tdepowersave CRASHED BIGTIME on start. I'll have to rebuild with full debug. I had not symbols in package.
DON'T PUSH -- SOMETHING NOT RIGHT
It builds fine, but craters on start.
You have updated dbus-1-tqt? See comment in bug 1597.
Rebuilding with tarballs from 2/1 hold on...
On 02/02/2014 01:47 PM, David C. Rankin wrote:
On 02/02/2014 01:13 PM, Slávek Banko wrote:
On Sunday 02 of February 2014 19:47:28 David C. Rankin wrote:
On 02/02/2014 11:12 AM, David C. Rankin wrote:
On 02/02/2014 09:50 AM, Slávek Banko wrote:
Late yesterday night I was finishing the last part. Now is a patch attached to the bug report 1597 - attachment 1910.
Please try it. I'll wait with pushing patch to GIT.
OK, will report back
Reporting back - tdepowersave CRASHED BIGTIME on start. I'll have to rebuild with full debug. I had not symbols in package.
DON'T PUSH -- SOMETHING NOT RIGHT
It builds fine, but craters on start.
You have updated dbus-1-tqt? See comment in bug 1597.
Rebuilding with tarballs from 2/1 hold on...
Ah.. Much better. tdepowersave is behaving. I've been through the config and everything checks out - I say push the commit.
Dne so 1. února 2014 David C. Rankin napsal(a):
On 02/01/2014 12:39 PM, Slávek Banko wrote:
I have tdepowersave on the two test virtual machines in KVM (first Debian 7.3 - Wheezy, second Ubuntu 13.10 - Saucy) and tdepowersave (with a patch, which I'm finishing) I have constantly at 0% CPU. On the real machine (with battery) I have not tested it yet.
Share the patch and I will help test :-)
To bug report 1597 I added another patch - addressing the lack of reaction on the lid closing. Please, test it.
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1597 http://bugs.pearsoncomputing.net/attachment.cgi?id=1953
-
David C. Rankin -
Slávek Banko