From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-July/006244.html | 73 ++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006244.html (limited to 'zarb-ml/mageia-dev/2011-July/006244.html') diff --git a/zarb-ml/mageia-dev/2011-July/006244.html b/zarb-ml/mageia-dev/2011-July/006244.html new file mode 100644 index 000000000..6f2339a7b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006244.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90? + + + + + + + + + +

[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?

+ Radu-Cristian FOTESCU + beranger5ca at yahoo.ca +
+ Fri Jul 1 19:37:55 CEST 2011 +

+
+ +
+
+> One way to figure that out is to attach gdb to it while it's running and 
+> then print a backtrace. If you do that several times, you may break in the code 
+> that's running a lot. But even if that works it is likely still not easy to 
+> figure out what's going on.
+> 
+> Other ways to get information would be to strace (or ltrace) this daemon to get 
+> an idea what it's trying to do. But CPU usage by the application itself 
+> cannot be seen this way.
+> 
+> An easier way to start is to run iotop and check if kded4 is doing any I/O 
+> related to this cpu usage.
+
+Well, thanks for the ideas. As long as it takes at least 55% of the CPU anyway, this is going to be quite cumbersome, and I have some other (productive) tasks to do, so I don't expect to investigate this before Sunday night.
+
+R-C
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1