1 |
On Tuesday 18 Oct 2011 22:52:56 Mick wrote: |
2 |
> Just woken up the box from sleep and within a minute I was alarmed by the |
3 |
> fan racing up and the temperature showing 71.0-76.0C |
4 |
> |
5 |
> Top showed that one of the two knotify processes was consuming 100% of CPU: |
6 |
> =============================================== |
7 |
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND |
8 |
> 6665 michael 21 1 299m 23m 16m S 100 0.6 6:27.02 kdeinit4: |
9 |
> kded4 [kdeinit] |
10 |
> 6709 michael 21 1 602m 36m 20m S 100 0.9 7:01.68 |
11 |
> /usr/bin/knotify4 2799 michael 21 1 579m 34m 20m S 1 0.9 |
12 |
> 0:05.13 /usr/bin/knotify4 |
13 |
=============================================== |
14 |
> |
15 |
> # lsof | grep -i /usr/bin/knotify4 |
16 |
> knotify4 2799 michael txt REG 8,7 176600 |
17 |
> 559245 /usr/bin/knotify4 |
18 |
> knotify4 6709 michael txt REG 8,7 176600 |
19 |
> 559245 /usr/bin/knotify4 |
20 |
> |
21 |
> I thought of sharing what I saw above as this is not happening that often |
22 |
> on my laptop. I know that others have also reported knotify playing up. |
23 |
> |
24 |
> The only KDE application that I was running after I woke up the machine |
25 |
> from sleep was kmail-1.13.7 (KDE-4.6.5) |
26 |
> |
27 |
> Is there an update on this problem that you know of? |
28 |
|
29 |
After some further investigation it is worth reporting that the problem was |
30 |
caused not by knotify, but by kdeinit! |
31 |
|
32 |
I exited X and stopped xdm. Only one knotify4 was left running as well as the |
33 |
kdeinit, both pegged at 100% and neither would go away after the X session had |
34 |
exited. I was able to kill -15 the knotify PID, but the kdeinit would not |
35 |
shift until I used kill -9. |
36 |
|
37 |
-- |
38 |
Regards, |
39 |
Mick |