Comment 87 for bug 93847

Revision history for this message
Thomas Weiler (thweiler) wrote :

Hi,

Important things first: I am not an expert and I am not a native speaker ;-)

But maybe I have hint about what could be going on here.

A short story about my problems with gnome-system-monitor:

I have used g-s-m on various machines and with diffrent Systems (Debian, Ubuntu, Fedora). I never had the problem with too high cpu usage until I bought a ThinkPad Edge last summer. I had on this machine Debian and Fedora (13 and 14). Everything worked fine exept the problem with g-s-m which this Thread is about.
So after 3 diffrent Systems I gave up and decided too use g-s-m no more. Instead of g-s-m I simply used top in the terminal.
Of course I used top only if I needed it and then only for a short time. G-s-m was ALWAYS running (task bar) !!!
After one week of happiness the following happened: I used top and it said 99,6% cpu usage for TOP!
I didnt touch the system (exept of the screenshot) for a few minutes. After one minute the cpu van started. I waited over one hour -> no change in cpu usage, until I restarted the system . After restart top worked again without any problems.
-> Screenshots

The following things are important:
-> top is a TERMINAL application so whatever causes the cpu usage has nothing to do with drawing lines in an X-Window app.
I don't know if g-s-m is based or has something to do with top.
-> If g-s-m has nothing to do with top this is NOT only a bug in g-s-m
-> This could be a general problem with determining the cpu-usage under pretty rare circumstances (dosen't happen very often) ------> Kernel?

I hope something of this makes sense, if somebody wants to know more about my system (processor, ...) just post here.

Thanks for reading