[opensuse-kde] [10.2/3.5.5] KDED using too much CPU
Top shows it running in the 50%-60% range. It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently. That setting is currently 78C/172F, and rebooting while the temp was elevated showed a temp of 70C, with similarly elevated temps on the other sensors. So far the only way I know to make the beeping stop is to drop to runlevel 3. After cooldown, fresh cleaning, reboot directly into BIOS, & 20 min uptime, temp is at 61C. The CPU is a socket 478 P4 3.0G, about 5 years old, but I don't remember whether Prescott or Northwood. Fans & heat sinks are all clean and working. How do I figure out what is making KDED use so much CPU, and stop it without having to log out? -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Il giovedì 11 dicembre 2008, Felix Miata scrisse:
Top shows it running in the 50%-60% range. It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently. That setting is currently 78C/172F, and rebooting while the temp was elevated showed a temp of 70C, with similarly elevated temps on the other sensors. So far the only way I know to make the beeping stop is to drop to runlevel 3. But 50/60% only for kded or total usage ?! I'm asking this because 70C with CPU at 50/60% is too high for me..
After cooldown, fresh cleaning, reboot directly into BIOS, & 20 min uptime, temp is at 61C.
I still think is too much. With my old athlon XP2800 overclocked, I reach 66C (in summer) after playing doom3 for few hours.. Try doom or something similar and see what happens.. Rebuilding the kernel (on another big software..) is another possible test..
The CPU is a socket 478 P4 3.0G, about 5 years old, but I don't remember whether Prescott or Northwood. Fans & heat sinks are all clean and working.
I dont know what to say, P4 CPUs heat like a nuclear plant. So all is possible..
How do I figure out what is making KDED use so much CPU, and stop it without having to log out?
Sorry, I don't know but follow my advice, change heat sink and/or fans.. Bye. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 2008/12/12 01:06 (GMT+0100) Daniele composed:
Il giovedì 11 dicembre 2008, Felix Miata scrisse:
Top shows it running in the 50%-60% range. It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently. That setting is currently 78C/172F, and rebooting while the temp was elevated showed a temp of 70C, with similarly elevated temps on the other sensors. So far the only way I know to make the beeping stop is to drop to runlevel 3.
But 50/60% only for kded or total usage ?!
kded was using 90%-95% of total usage.
I'm asking this because 70C with CPU at 50/60% is too high for me..
http://processorfinder.intel.com/details.aspx?sSpec=SL79L is probably my CPU, with a design spec of 69.1C.
After cooldown, fresh cleaning, reboot directly into BIOS, & 20 min uptime, temp is at 61C.
I still think is too much. With my old athlon XP2800 overclocked, I reach 66C (in summer) after playing doom3 for few hours..
Comparing AMD to Intel regarding temps is pointless.
Try doom or something similar and see what happens..
The box only runs SUSE. I don't play games on any box, and don't know anything about Doom.
Rebuilding the kernel (on another big software..) is another possible test..
I built kernels on it a while back. IIRC it never touched that level of temperature or CPU usage. Kernel building is a lot more disk I/O dependent than I imagine kded is.
The CPU is a socket 478 P4 3.0G, about 5 years old, but I don't remember whether Prescott or Northwood. Fans & heat sinks are all clean and working.
I dont know what to say, P4 CPUs heat like a nuclear plant. So all is possible..
They're not all the same. The one I have (Prescott @ 3.0GHz) is one of the most effective heat generators of them all. Months or a year ago it had a problem with heat generation, and I underclocked it several weeks to solve the problem pending a new CPU cooler, which stopped the beeps and stopped the random BIOS overtemp-forced shutdowns.
How do I figure out what is making KDED use so much CPU, and stop it without having to log out?
Sorry, I don't know but follow my advice, change heat sink and/or fans..
The cooler is supposed to be good enough for 3.6GHz. The fans are all working as designed. The problem does not occur under normal usage, only when a runaway process works the CPU intensively. http://lists.kde.org/?l=kde-linux&m=122904262017936&w=2 is a reply to my same question on the kde-linux list that offers an apparent solution. The ultimate solution is system replacement. I already built it weeks ago. I just have to get an OS chosen and installed, the former of which has been proving difficult due to my mandatory requirement for X to have functioning panning virtual desktops, AFAICT missing from openSUSE 11.0 & 11.1 and other xrandr distros released in the past year or more. -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
But 50/60% only for kded or total usage ?!
kded was using 90%-95% of total usage.
...
It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently.
You have to different problems: · One, that kded is using too much cpu. · Two, your cooling system can't cope. The cpu cooling system has to be able to keep the cpu below the maximum temp even if it runs at 100% load full time. If that is not possible, the CPU or the operating system should be able to take measures like lowering the cpu frequency and/or decreasing the load (idle cycles, for instance), but I'm not aware of whether Linux can do this. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklHAPcACgkQtTMYHG2NR9VSAQCff5m4U3o1Frq4m9JMDnhtOKtW UHoAoJbeuXusx6KbsTAof38HvwyTepfe =MTjj -----END PGP SIGNATURE-----
On 2008/12/16 02:14 (GMT+0100) Carlos E. R. composed:
On Thursday, 2008-12-11 at 23:23 -0500, Felix Miata wrote:
But 50/60% only for kded or total usage ?!
kded was using 90%-95% of total usage.
It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently.
You have to different problems:
· One, that kded is using too much cpu.
Sort of. This has only happened twice. Total CPU ATM is 0.3%. I don't know how to trigger it, and thus can take no steps to find its source. If and when that happens, I can try the steps Dirk Müller provided upthread.
· Two, your cooling system can't cope.
1-It does well enough under normal justifiable load conditions. Without KDED looping, load rarely goes above 10% for more than a few seconds at a time. 2-The box is 5 years old and on 10.2. I never could figure out how to get sensors to work on it. A replacement box has already been built. I'm just trying to figure out which OS to install before installing and placing in service. ATM I'm looking for a workaround to http://bugs.freedesktop.org/show_bug.cgi?id=11418 so that I can use 11.1. If I can't it appears I'll have to goto 10.3 and hope that bug gets fixed before 11.2 gets released. On the new box I think the BIOS can slow down the CPU automatically if temp goes above threshhold temp if the OS cannot.
The cpu cooling system has to be able to keep the cpu below the maximum temp even if it runs at 100% load full time. If that is not possible, the CPU or the operating system should be able to take measures like lowering the cpu frequency and/or decreasing the load (idle cycles, for instance), but I'm not aware of whether Linux can do this. -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV
Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday 15 December 2008 19:42:16 Felix Miata wrote:
On the new box I think the BIOS can slow down the CPU automatically if temp goes above threshhold temp if the OS cannot.
Only if CPU frequency scaling is supported, but Linux takes over that function anyway. I know that I can switch between max and 50% on a AMD 64 based laptop running 10.3. Though, main point is that cooling should keep CPU in allowed temp range even if it runs 100% all the time. The problem is not only that heath sink and fans should be clean, but also thermal compound should be the good one. Silver is better then white, and white is cheaper, so you can imagine which one is factory default ;-) -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2008-12-15 a las 20:59 -0600, Rajko Matovic escribió: ...
Though, main point is that cooling should keep CPU in allowed temp range even if it runs 100% all the time.
Absolutely.
The problem is not only that heath sink and fans should be clean, but also thermal compound should be the good one. Silver is better then white, and white is cheaper, so you can imagine which one is factory default ;-)
Or, if the heat sink is of the gas kind (vapour), and it has a leak, it behaves much worse than a solid metal heat sink. - -- Saludos Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklHHDgACgkQtTMYHG2NR9V8ugCbBLQYDxx/WVKioait29ciTJ4T OF4An0oUh2oCFpmXS0a2gMYq28EdGuiA =n05W -----END PGP SIGNATURE-----
On Thursday 11 December 2008, Felix Miata wrote:
Top shows it running in the 50%-60% range. It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently.
is this a new issue (after installing an online update for example) or did you have it for a longer time?
How do I figure out what is making KDED use so much CPU, and stop it without having to log out?
please post the output of "dcop kded kded loadedModules" you can try to figure out which module causes the issue by calling "dcop kded kded unloadModule <foo>",where foo is one of the strings that you get from the loadedModules above. by unloading one after the other, and comparing in top(1), you should be really easy able to figure out which module causes it. when you know, we can figure out more. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 2008/12/12 12:29 (GMT+0100) Dirk Müller composed:
On Thursday 11 December 2008, Felix Miata wrote:
Top shows it running in the 50%-60% range. It's sending my CPU temp up high enough to bump the BIOS overheat warning frequently.
is this a new issue (after installing an online update for example) or did you have it for a longer time?
This has only happened twice that I can recall, both in past couple of days. Last update was a short, hand-picked amount of apps, hoping to avoid breaking the stability I've enjoyed for months. Tail of /var/log/YaST2/y2logRPM: http://fm.no-ip.com/tmp/SUSE/logs/YaST/y2logRPM-A865,txt
How do I figure out what is making KDED use so much CPU, and stop it without having to log out?
please post the output of "dcop kded kded loadedModules"
Right now that produces: mediamanager remotedirnotify dnssdwatcher konqy_preloader kinetd medianotifier systemdirnotify homedirnotify networkstatus favicons kwrited khotkeys But, I presume you mean when I can reproduce. ;-) I shut down the machine to check BIOS temps, fans and clean again, and it hasn't yet happened again. I have a hunch that it's related to DVD insertion/knotify. The first instance happened only after the problem reported in http://lists.kde.org/?l=kde-linux&m=122875116924368&w=2 after which I remember Konq complaining on automatic opening on blank DVD insertion (at the request of K3B). Over the next several days I should be performing similar non-routine activity again.
you can try to figure out which module causes the issue by calling
"dcop kded kded unloadModule <foo>",where foo is one of the strings that you get from the loadedModules above. by unloading one after the other, and comparing in top(1), you should be really easy able to figure out which module causes it.
when you know, we can figure out more.
Thanks! -- "Unless the Lord builds the house, its builders labor in vain." Psalm 127:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (5)
-
Carlos E. R. -
Daniele -
Dirk Müller -
Felix Miata -
Rajko Matovic