Hmmm I have been wondering what is killing my system performance, and found that a root process - kdeinit - is chewing up well over 50% of my CPU time. I can su to root and kill -9 the process without affecting my system.. nothing seems to stop working or anything like that, and my processor immediately returns to idle. Any ideas why kdeinit stays hanging about and consuming so much CPU cycle time? C.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 18 February 2002 20:20, Clayton Cornell wrote:
Hmmm I have been wondering what is killing my system performance, and found that a root process - kdeinit - is chewing up well over 50% of my CPU time. I can su to root and kill -9 the process without affecting my system.. nothing seems to stop working or anything like that, and my processor immediately returns to idle.
Any ideas why kdeinit stays hanging about and consuming so much CPU cycle time?
C. What kde version do you use?
Fifty flippant frogs Walked by on flippered feet And with their slime they made the time Unnaturally fleet. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8cWRZAEYnIVU7X9IRAtngAKCCmZ3iwOO6HHQVhjaKOvPuvLGe9QCfUuGM CBiephh/rdx+bFIC3xitWUE= =/7nS -----END PGP SIGNATURE-----
Are you running a different Window Manager / Desktop and running something like Konqueror? For some odd reason kdeinit doesn't go away when you close Konq in this situation. If your running KDE2 and it's happening then yeah..we would need to know the version and what your doing when it goes nuts. ;) * Clayton Cornell (c.cornell@chello.nl) [020218 12:20]: ->Hmmm I have been wondering what is killing my system performance, and found ->that a root process - kdeinit - is chewing up well over 50% of my CPU time. ->I can su to root and kill -9 the process without affecting my system.. ->nothing seems to stop working or anything like that, and my processor ->immediately returns to idle. -> ->Any ideas why kdeinit stays hanging about and consuming so much CPU cycle ->time? -> ->C. -> -> ->-- ->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the FAQ at http://www.suse.com/support/faq and the ->archives at http://lists.suse.com -> -----=====-----=====-----=====-----=====----- Ben Rosenberg mailto:ben@whack.org -----=====-----=====-----=====-----=====----- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC
Doh! I should have known better and given more information. Running a vanilla install of SuSE7.3, and KDE2.2.1 As for what's going on when if goes nuts... not much. I re-boot the system roughly once every 48 hours because I have to run Windows for a few minutes every other day or so. Anyway, I noticed the kdeinit thing after two separate boots. Everything starts up nicely without any errors. I have KMail and eDonkey running all the time - neither of which consume a lot of CPU power. I use Konq. as the main web browser, followed by Opera when Konq fails me. I don't notice a specific event when kdeinit starts chewing up CPU time. I will be doing the basics - reading email, browsing a few websites. At some point I will notice a growing red bar (the one for CPU load) on the KTimeMon applet in the task bar. This coincides with my system slowing down to Windows speeds. This is when I go hunting. Top reports back the one running root process kdeinit, and it is slowly chewing up CPU % If I leave it to see if it cleans up after itself - a few hours where I went and did something else - it just continues to eat %'s, going from maybe 40% CPU to 60%. I stopped it there, su'ed to root and kill -9'ed it. That's about all I can think of.... C. On Tuesday 19 February 2002 03:33, Ben Rosenberg wrote:
Are you running a different Window Manager / Desktop and running something like Konqueror? For some odd reason kdeinit doesn't go away when you close Konq in this situation. If your running KDE2 and it's happening then yeah..we would need to know the version and what your doing when it goes nuts. ;)
* Clayton Cornell (c.cornell@chello.nl) [020218 12:20]: ->Hmmm I have been wondering what is killing my system performance, and found ->that a root process - kdeinit - is chewing up well over 50% of my CPU time. ->I can su to root and kill -9 the process without affecting my system.. ->nothing seems to stop working or anything like that, and my processor ->immediately returns to idle. -> ->Any ideas why kdeinit stays hanging about and consuming so much CPU cycle ->time? -> ->C. -> -> ->-- ->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the FAQ at http://www.suse.com/support/faq and the ->archives at http://lists.suse.com ->
-----=====-----=====-----=====-----=====----- Ben Rosenberg mailto:ben@whack.org -----=====-----=====-----=====-----=====----- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC
That's about all I can think of....
kdeinit is just a "fast-start" wrapper around <something>. Next time it happens, do a 'ps auxww' and give us the whole line (i.e. the parameters to the bad kdeinit). This will help pin down what the <something> is that's causing the trouble. -- 8:55am up 6 days, 37 min, 1 user, load average: 0.00, 0.02, 0.00
participants (4)
-
Ben Rosenberg -
Clayton Cornell -
Derek Fountain -
Tom Wesley