cpu being pegged at 100%

[ppberns]

Hi,
I just noticed this happening to my system (amd x2 64) and was wondering if anyone can shed a little light on it.
When I reboot my system (either soft or hard) after I log in I run the top command in a terminal and see the following:

top - 11:47:22 up 16 min, 1 user, load average: 1.18, 1.14, 0.78
Tasks: 140 total, 3 running, 137 sleeping, 0 stopped, 0 zombie
Cpu(s): 55.1%us, 1.3%sy, 0.0%ni, 33.9%id, 9.3%wa, 0.0%hi, 0.3%si, 0.0%st
Mem: 2062996k total, 804556k used, 1258440k free, 24472k buffers
Swap: 0k total, 0k used, 0k free, 426732k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8314 ppberns 20 0 115m 13m 11m R 100 0.7 15:09.22 kdesu

It stays that way till I kill the process (8314). It really bogs the system down till I kill it. Now I have ran lsof -p 8314 and got the following:

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
kdesu 8314 ppberns cwd DIR 8,3 4096 32769 /home/ppberns
kdesu 8314 ppberns rtd DIR 8,4 4096 2 /
kdesu 8314 ppberns txt REG 8,4 77976 12191965 /usr/bin/kdesudo
kdesu 8314 ppberns mem REG 8,4 79104 12371909 /usr/lib/kde3/plugins/styles/highcolor.so
kdesu 8314 ppberns mem REG 8,4 47528 138068 /lib/libnss_files-2.7.so
kdesu 8314 ppberns mem REG 8,4 43480 138094 /lib/libnss_nis-2.7.so
kdesu 8314 ppberns mem REG 8,4 93080 138065 /lib/libnsl-2.7.so
kdesu 8314 ppberns mem REG 8,4 35632 138066 /lib/libnss_compat-2.7.so
kdesu 8314 ppberns mem REG 8,4 20128 12190077 /usr/lib/libXdmcp.so.6.0.0
kdesu 8314 ppberns mem REG 8,4 112080 12189926 /usr/lib/libxcb.so.1.0.0
kdesu 8314 ppberns mem REG 8,4 5864 12189928 /usr/lib/libxcb-xlib.so.0.0.0
kdesu 8314 ppberns mem REG 8,4 9736 12190073 /usr/lib/libXau.so.6.0.0

<------------- Lots of stuff deleted here ---------------------->

kdesu 8314 ppberns mem REG 8,4 13224 3883032 /var/cache/fontconfig/6386b86020ecc1ef9690bb720a13964f-x86-64.cache-2
kdesu 8314 ppberns mem REG 8,4 46248 3883025 /var/cache/fontconfig/089dead882dea3570ffc31a9898cfb69-x86-64.cache-2
kdesu 8314 ppberns mem REG 8,4 40120 3883015 /var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-x86-64.cache-2
kdesu 8314 ppberns mem REG 8,4 254076 145129 /usr/lib/locale/en_US.utf8/LC_CTYPE
kdesu 8314 ppberns mem REG 8,4 921214 145130 /usr/lib/locale/en_US.utf8/LC_COLLATE
kdesu 8314 ppberns 0r FIFO 0,5 20868 pipe
kdesu 8314 ppberns 1w REG 8,3 7618 33341 /home/ppberns/.xsession-errors
kdesu 8314 ppberns 2w REG 8,3 7618 33341 /home/ppberns/.xsession-errors
kdesu 8314 ppberns 3u unix 0xffff810069317340 21707 socket
kdesu 8314 ppberns 4u unix 0xffff81006921ab00 21709 socket
kdesu 8314 ppberns 5r FIFO 0,5 21711 pipe
kdesu 8314 ppberns 6w FIFO 0,5 21711 pipe
kdesu 8314 ppberns 7r FIFO 0,5 21713 pipe
kdesu 8314 ppberns 8r FIFO 0,5 20684 pipe
kdesu 8314 ppberns 9w FIFO 0,5 20684 pipe
kdesu 8314 ppberns 10w FIFO 0,5 21713 pipe
kdesu 8314 ppberns 11u unix 0xffff81006921b600 21717 socket
kdesu 8314 ppberns 13u unix 0xffff81007d7c78c0 20745 /tmp/seahorse-UnQbzd/S.gpg-agent

It appears like the system is doing some house cleaning but this just started happening this past week and it doesn't end on it's own (at least not after a few hours). Why is the system doing this and why do I have to kill it?? And yes I have checked the crontab, at, schedules, etc.

Thanks

[Snowhog]

Re: cpu being pegged at 100%

Are you running HH remix (KDE 4.x) or HH w/KDE 3.5.9? The running process - kdesu - is of course, the command to execute (as root) a GUI application. Assuming that you are seeing this after boot/login, it would imply that at some previous time you had initiated this command from the CLI and never exited it?? Hmm. Have you checked your Autostart (hidden) folder?

[dibl]

Re: cpu being pegged at 100%

Yes, I have observed that exact problem once before, a few weeks ago. There is a post on this forum about it. It has never happened again. I suspect it is related to the KDE3.5.9 --> KDE4 transition.

I had a similar incident this morning and discovered npviewer.bin hogging 90% of the CPU -- an Adobe flashplayer bug, unfortunately.

[ppberns]

Re: cpu being pegged at 100%

Hi,

Thanks to all who responded. It's nice to know I'm not alone. I am running kde 3.5.9 although I do have kde 4.1 loaded on the system. I did try it for about 15 minutes a couple of days ago and then haven't turned it on since. I have noticed that now after killing that process and then rebooting a couple more times, it has stop showing up in the "top" listings. I guess whatever the bug was/is that got me is now gone (at least until the next time I try kde4.1). :-)

Thanks again.