blob: 6f2339a7b4e97aa762e97396b6b5506a426c014f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Anybody%20having%20high%20CPU%20by%20kded4%20after%20upgrading%0A%09to%204.6.90%3F&In-Reply-To=%3C1309541875.98985.YahooMailNeo%40web161704.mail.bf1.yahoo.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006243.html">
<LINK REL="Next" HREF="006255.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?</H1>
<B>Radu-Cristian FOTESCU</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Anybody%20having%20high%20CPU%20by%20kded4%20after%20upgrading%0A%09to%204.6.90%3F&In-Reply-To=%3C1309541875.98985.YahooMailNeo%40web161704.mail.bf1.yahoo.com%3E"
TITLE="[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?">beranger5ca at yahoo.ca
</A><BR>
<I>Fri Jul 1 19:37:55 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006243.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</A></li>
<LI>Next message: <A HREF="006255.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6244">[ date ]</a>
<a href="thread.html#6244">[ thread ]</a>
<a href="subject.html#6244">[ subject ]</a>
<a href="author.html#6244">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
><i> One way to figure that out is to attach gdb to it while it's running and
</I>><i> then print a backtrace. If you do that several times, you may break in the code
</I>><i> that's running a lot. But even if that works it is likely still not easy to
</I>><i> figure out what's going on.
</I>><i>
</I>><i> Other ways to get information would be to strace (or ltrace) this daemon to get
</I>><i> an idea what it's trying to do. But CPU usage by the application itself
</I>><i> cannot be seen this way.
</I>><i>
</I>><i> An easier way to start is to run iotop and check if kded4 is doing any I/O
</I>><i> related to this cpu usage.
</I>
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
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006243.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</A></li>
<LI>Next message: <A HREF="006255.html">[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6244">[ date ]</a>
<a href="thread.html#6244">[ thread ]</a>
<a href="subject.html#6244">[ subject ]</a>
<a href="author.html#6244">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
