6 Mar
2014
6 Mar
'14
2:31 p.m.
On 03/06/2014 12:29 PM, Timothy Pearson wrote:
Here is where the tdepowersave generates all the error
(TQEventLoop::activateTimers) :
TQTimerEvent (timerId=122, this=0xbf894650) at kernel/ntqevent.h:169
169 kernel/ntqevent.h: No such file or directory.
TQEventLoop::activateTimers (this=this@entry=0x98a9d38) at
kernel/qeventloop_unix.cpp:564
564 kernel/qeventloop_unix.cpp: No such file or directory.
TQApplication::sendEvent (receiver=0x9977db0, event=event@entry=0xbf894650) at
kernel/qapplication.cpp:2456
2456 kernel/qapplication.cpp: No such file or directory.
2457 in kernel/qapplication.cpp
TQEventLoop::activateTimers (this=this@entry=0x98a9d38) at
kernel/qeventloop_unix.cpp:565
565 kernel/qeventloop_unix.cpp: No such file or directory.
--
David C. Rankin, J.D.,P.E.
On 03/06/2014
10:52 AM, Dr. Nikolaus Klepp wrote:
Try attaching gdb to the runaway tdepowersave process--that should at
least show you where it is stuck.
Tim
Am Donnerstag, 6. März 2014 schrieb David C.
Rankin:
Kernel is 3.13-5.1 (just a few days old), So this is happening with
current kernels.
--
David C. Rankin, J.D.,P.E. All,
Testing the new soft-freeze packages has disclosed a horrible problem
with
tdepowersave taking nearly 100% of the CPU. My laptop was nearly on
fire this
morning:
[screenshot]
http://www.3111skyline.com/dl/dt/trinity/ss/tdeowersave-97percent.jpg
Earlier in development I saw tdepowesave in the 20-40% range, but
never at
near 100% of CPU. What to try?
What kernel do you use? I had the same problem on wheezy with 3.5.13.2.
tdepowersave took 100% of one core. It occured after tdepowersave put
the x61 to powersave the second time. It looks like the problem went
away after changing to kernel 3.12-0.bpo.1.
nik
