100%

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
lawngnome
Level 1
Level 1
Posts: 2
Joined: Mon Jun 18, 2007 1:19 am

100%

Post by lawngnome »

I have installed Mint and have been playing with it off and on over the last month and love it. i working on a few things that bother me like getting my zen vision W to run on it. and then i looked at my system monitor today because my lap was getting hot an my CPU is running at a constant 100%. I was hoping some one could tell me how to throttle it down a bit. and all i have running is firefox.


http://i101.photobucket.com/albums/m67/ ... onitor.png

scorp123
Level 8
Level 8
Posts: 2272
Joined: Sat Dec 02, 2006 4:19 pm
Location: Switzerland

Post by scorp123 »

That screenshot doesn't really help as it contains zero useful information :?

Instead, could you please try this:

- as soon as this happens again: Open a terminal
- maximize the terminal
- and then type this command into it: top

Mark the output you get with your mouse and then paste it here. It should look something like this:

Code: Select all

top - 21:07:04 up  1:11,  3 users,  load average: 0.00, 0.02, 0.00
Tasks: 124 total,   1 running, 123 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.6%us,  0.2%sy,  0.0%ni, 98.3%id,  0.7%wa,  0.0%hi,  0.1%si,  0.0%st
Mem:   1026004k total,   503644k used,   522360k free,    15400k buffers
Swap:  1855468k total,        0k used,  1855468k free,   282632k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                         
    1 root      16   0  1740  804  584 S    0  0.1   0:01.44 init                                                            
    2 root      RT   0     0    0    0 S    0  0.0   0:00.00 migration/0                                                     
    3 root      34  19     0    0    0 S    0  0.0   0:00.05 ksoftirqd/0                                                     
    4 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/0                                                      
    5 root      RT   0     0    0    0 S    0  0.0   0:00.00 migration/1                                                     
    6 root      36  19     0    0    0 S    0  0.0   0:00.00 ksoftirqd/1                                                     
    7 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/1                                                      
    8 root      10  -5     0    0    0 S    0  0.0   0:00.06 events/0                                                        
    9 root      10  -5     0    0    0 S    0  0.0   0:00.02 events/1                                                        
   10 root      10  -5     0    0    0 S    0  0.0   0:00.00 khelper                                                         
   11 root      10  -5     0    0    0 S    0  0.0   0:00.00 kthread                                                         
   35 root      10  -5     0    0    0 S    0  0.0   0:00.00 kblockd/0                                                       
   36 root      10  -5     0    0    0 S    0  0.0   0:00.00 kblockd/1                                                       
   37 root      16  -5     0    0    0 S    0  0.0   0:00.00 kacpid                                                          
   38 root      16  -5     0    0    0 S    0  0.0   0:00.00 kacpi_notify                                                    
  169 root      10  -5     0    0    0 S    0  0.0   0:00.05 kseriod                                                         
  198 root      16   0     0    0    0 S    0  0.0   0:00.00 pdflush                                                         
  199 root      15   0     0    0    0 S    0  0.0   0:00.00 pdflush                                                         
  200 root      11  -5     0    0    0 S    0  0.0   0:00.00 kswapd0                                                         
  201 root      11  -5     0    0    0 S    0  0.0   0:00.00 aio/0                                                           
  202 root      11  -5     0    0    0 S    0  0.0   0:00.00 aio/1                                                           
  834 root      15   0     0    0    0 S    0  0.0   0:00.00 kirqd                                                           
 2058 root      10  -5     0    0    0 S    0  0.0   0:00.00 ksuspend_usbd                                                   
 2059 root      10  -5     0    0    0 S    0  0.0   0:00.00 khubd                                                           
 2078 root      10  -5     0    0    0 S    0  0.0   0:00.00 khpsbpkt                                                        
 2095 root      10  -5     0    0    0 S    0  0.0   0:01.18 ata/0                                                           
 2096 root      10  -5     0    0    0 S    0  0.0   0:00.10 ata/1                                                           
 2097 root      18  -5     0    0    0 S    0  0.0   0:00.00 ata_aux                                                         
 2226 root      10  -5     0    0    0 S    0  0.0   0:00.00 knodemgrd_0                                                     
 2273 root      10  -5     0    0    0 S    0  0.0   0:00.00 scsi_eh_0
This list would show which process is eating away the CPU ...

Another one you could try: ps -efH

The output you get should be something like this:

Code: Select all

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 19:55 ?        00:00:01 /sbin/init
root         2     1  0 19:55 ?        00:00:00   [migration/0]
root         3     1  0 19:55 ?        00:00:00   [ksoftirqd/0]
root         4     1  0 19:55 ?        00:00:00   [watchdog/0]
root         5     1  0 19:55 ?        00:00:00   [migration/1]
root         6     1  0 19:55 ?        00:00:00   [ksoftirqd/1]
root         7     1  0 19:55 ?        00:00:00   [watchdog/1]
root         8     1  0 19:55 ?        00:00:00   [events/0]
root         9     1  0 19:55 ?        00:00:00   [events/1]
root        10     1  0 19:55 ?        00:00:00   [khelper]
root        11     1  0 19:55 ?        00:00:00   [kthread]
root        35    11  0 19:55 ?        00:00:00     [kblockd/0]
root        36    11  0 19:55 ?        00:00:00     [kblockd/1]
root        37    11  0 19:55 ?        00:00:00     [kacpid]
root        38    11  0 19:55 ?        00:00:00     [kacpi_notify]
root       169    11  0 19:55 ?        00:00:00     [kseriod]
root       198    11  0 19:55 ?        00:00:00     [pdflush]
root       199    11  0 19:55 ?        00:00:00     [pdflush]
root       200    11  0 19:55 ?        00:00:00     [kswapd0]
root       201    11  0 19:55 ?        00:00:00     [aio/0]
root       202    11  0 19:55 ?        00:00:00     [aio/1]
root      2058    11  0 19:55 ?        00:00:00     [ksuspend_usbd]
root      2059    11  0 19:55 ?        00:00:00     [khubd]
root      2078    11  0 19:55 ?        00:00:00     [khpsbpkt]
root      2095    11  0 19:55 ?        00:00:01     [ata/0]
root      2096    11  0 19:55 ?        00:00:00     [ata/1]
root      2097    11  0 19:55 ?        00:00:00     [ata_aux]
root      2226    11  0 19:55 ?        00:00:00     [knodemgrd_0]
root      2273    11  0 19:55 ?        00:00:00     [scsi_eh_0]
root      2274    11  0 19:55 ?        00:00:00     [scsi_eh_1]
root      2275    11  0 19:55 ?        00:00:00     [scsi_eh_2]
root      2276    11  0 19:55 ?        00:00:00     [scsi_eh_3]
root      2352    11  0 19:55 ?        00:00:00     [scsi_eh_4]
root      2353    11  0 19:55 ?        00:00:00     [scsi_eh_5]
root      2525    11  0 19:55 ?        00:00:00     [kjournald]
root      3626    11  0 19:55 ?        00:00:00     [kpsmoused]
root      3720    11  0 19:55 ?        00:00:00     [kmmcd]
root      3756    11  0 19:55 ?        00:00:00     [pccardd]
root      3956    11  0 19:55 ?        00:00:00     [hda_codec]
root      4160    11  0 19:55 ?        00:00:00     [kjournald]
root      4162    11  0 19:55 ?        00:00:00     [kjournald]
root      4164    11  0 19:55 ?        00:00:00     [kjournald]
root      4166    11  0 19:55 ?        00:00:00     [kjournald]
root      5385    11  0 19:56 ?        00:00:00     [kondemand/0]
root      5386    11  0 19:56 ?        00:00:00     [kondemand/1]
root       834     1  0 19:55 ?        00:00:00   [kirqd]
root      2685     1  0 19:55 ?        00:00:00   /sbin/udevd --daemon
root      4544     1  0 19:56 tty4     00:00:00   /sbin/getty 38400 tty4
root      4545     1  0 19:56 tty5     00:00:00   /sbin/getty 38400 tty5
root      4550     1  0 19:56 tty3     00:00:00   /sbin/getty 38400 tty3
root      4551     1  0 19:56 tty1     00:00:00   /sbin/getty 38400 tty1
root      4552     1  0 19:56 tty6     00:00:00   /sbin/getty 38400 tty6
root      4841     1  0 19:56 ?        00:00:00   /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket
root      4951     1  0 19:56 ?        00:00:00   /sbin/syslogd
root      5006     1  0 19:56 ?        00:00:00   /bin/dd bs 1 if /proc/kmsg of /var/run/klogd/kmsg
klog      5008     1  0 19:56 ?        00:00:00   /sbin/klogd -P /var/run/klogd/kmsg
103       5029     1  0 19:56 ?        00:00:00   /usr/bin/dbus-daemon --system
107       5045     1  0 19:56 ?        00:00:00   /usr/sbin/hald
root      5046  5045  0 19:56 ?        00:00:00     hald-runner
107       5052  5046  0 19:56 ?        00:00:00       hald-addon-keyboard: listening on /dev/input/event1
107       5053  5046  0 19:56 ?        00:00:00       hald-addon-keyboard: listening on /dev/input/event5
root      5055  5046  0 19:56 ?        00:00:00       /usr/lib/hal/hald-addon-cpufreq
107       5056  5046  0 19:56 ?        00:00:00       hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
107       5057  5046  0 19:56 ?        00:00:00       hald-addon-keyboard: listening on /dev/input/event6
107       5058  5046  0 19:56 ?        00:00:00       hald-addon-keyboard: listening on /dev/input/event7
107       5072  5046  0 19:56 ?        00:00:00       hald-addon-storage: polling /dev/scd0 (every 2 sec)
root      5085     1  0 19:56 ?        00:00:00   /usr/sbin/dhcdbd --system
dhcp      5971  5085  0 19:57 ?        00:00:00     /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.ath0.leases -pf /var/run/dh
root      5100     1  0 19:56 ?        00:00:00   /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.
avahi     5117     1  0 19:56 ?        00:00:00   avahi-daemon: running [pegasus.local]
avahi     5118  5117  0 19:56 ?        00:00:00     avahi-daemon: chroot helper
root      5132     1  0 19:56 ?        00:00:00   /usr/sbin/NetworkManagerDispatcher --pid-file /var/run/NetworkManager/Netwo
root      5145     1  0 19:56 ?        00:00:00   /usr/bin/system-tools-backends
root      5146  5145  0 19:56 ?        00:00:00     dbus-daemon --session --print-address --nofork
root      5198     1  0 19:56 ?        00:00:00   /usr/sbin/gdm
root      5201  5198  0 19:56 ?        00:00:00     /usr/sbin/gdm
root      5202  5201  0 19:56 tty7     00:00:15       /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten
adm       5810  5201  0 19:57 ?        00:00:00       x-session-manager
adm       5852  5810  0 19:57 ?        00:00:00         /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session
adm       5873  5810  0 19:57 ?        00:00:02         /usr/bin/metacity --sm-client-id=default0
adm       5878  5810  0 19:57 ?        00:00:02         gnome-panel --sm-client-id default1
adm       5882  5810  0 19:57 ?        00:00:01         nautilus --no-default-window --sm-client-id default2
adm       5891  5810  0 19:57 ?        00:00:00         update-notifier
adm       5899  5810  0 19:57 ?        00:00:00         /usr/lib/evolution/2.10/evolution-alarm-notify
adm       5900  5810  0 19:57 ?        00:00:00         glipper
adm       5902  5810  0 19:57 ?        00:00:00         python /usr/share/system-config-printer/applet.py
adm       5903  5810  0 19:57 ?        00:00:00         nm-applet --sm-disable
adm       5904  5810  0 19:57 ?        00:00:00         gnome-cups-icon --sm-client-id default3
cupsys    5272     1  0 19:56 ?        00:00:00   /usr/sbin/cupsd
root      5296     1  0 19:56 ?        00:00:00   /usr/sbin/hpiod
hplip     5299     1  0 19:56 ?        00:00:00   python /usr/sbin/hpssd
root      5363     1  0 19:56 ?        00:00:00   /usr/sbin/inetd
root      5413     1  0 19:56 ?        00:00:00   /usr/sbin/sshd
root      5481     1  0 19:56 ?        00:00:00   /usr/sbin/hcid -x -s
root      5496     1  0 19:56 ?        00:00:00   [krfcommd]
daemon    5534     1  0 19:56 ?        00:00:00   /usr/sbin/atd
root      5550     1  0 19:56 ?        00:00:00   /usr/sbin/cron
104       5706     1  0 19:56 ?        00:00:00   avahi-autoipd: [eth0] bound 169.254.8.214
root      5707  5706  0 19:56 ?        00:00:00     avahi-autoipd: [eth0] callout dispatcher
dhcp      5747     1  0 19:56 ?        00:00:00   dhclient3 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.l
root      5803     1  0 19:57 tty2     00:00:00   /sbin/getty 38400 tty2
adm       5807     1  0 19:57 ?        00:00:00   /usr/bin/gnome-keyring-daemon
adm       5855     1  0 19:57 ?        00:00:00   /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 8 --session
adm       5856     1  0 19:57 ?        00:00:00   /usr/bin/dbus-launch --exit-with-session x-session-manager
adm       5858     1  0 19:57 ?        00:00:00   /usr/lib/libgconf2-4/gconfd-2 6
adm       5861     1  0 19:57 ?        00:00:00   /usr/lib/control-center/gnome-settings-daemon
adm       5868     1  0 19:57 ?        00:00:00   /bin/sh -c /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 24
adm       5869  5868  0 19:57 ?        00:00:00     /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 24
adm       5885     1  0 19:57 ?        00:00:00   /usr/lib/bonobo-activation/bonobo-activation-server --ac-activate --ior-out
adm       5887     1  0 19:57 ?        00:00:00   gnome-volume-manager --sm-client-id default4
adm       5890     1  0 19:57 ?        00:00:00   /usr/lib/gnome-vfs-2.0/gnome-vfs-daemon
adm       5905     1  0 19:57 ?        00:00:00   gnome-power-manager
adm       5912     1  0 19:57 ?        00:00:00   /usr/lib/gnome-applets/trashapplet --oaf-activate-iid=OAFIID:GNOME_Panel_Tr
adm       5931     1  0 19:57 ?        00:00:00   /usr/lib/nautilus-cd-burner/mapping-daemon
root      5934     1  0 19:57 ?        00:00:00   /sbin/wpa_supplicant -dd -g /var/run/wpa_supplicant-global
adm       5967     1  0 19:57 ?        00:00:00   /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerA
adm       6023     1  0 19:57 ?        00:00:00   /usr/lib/notification-daemon/notification-daemon
adm       6038     1  0 19:58 ?        00:00:01   gnome-screensaver
adm       6096     1  0 20:00 ?        00:00:21   /usr/lib/firefox/firefox-bin
adm       6162     1  0 20:01 ?        00:00:00   gnome-terminal
adm       6165  6162  0 20:01 ?        00:00:00     gnome-pty-helper
adm       6166  6162  0 20:01 pts/0    00:00:00     bash
adm       6225  6162  0 20:02 pts/1    00:00:00     bash
adm       7943  6225  0 21:08 pts/1    00:00:00       ps -efH
This list shows which process spawned which other process ... So the two lists combined can be very helpful to find out what's eating away all those CPU cycles.

User avatar
clem
Level 12
Level 12
Posts: 4151
Joined: Wed Nov 15, 2006 8:34 am
Contact:

Post by clem »

Beagle indexes files when the CPU is idle.. so here's your number one suspect :) As Scorp123 said, top should tell you anyway.

Clem
Image

lawngnome
Level 1
Level 1
Posts: 2
Joined: Mon Jun 18, 2007 1:19 am

Post by lawngnome »

i feel so retarded. i restarted the machine after posting and now it has dropped 7.6% and i had a "Zombie" program running??

well when i was running at 100% it was during a time when i needed to up date the machine. could the auto update have something to do with the cpu usage.

I'm So sorry about t his i really am a n00b at linux and i consider my self an above avrage computer user and now i can't duplicate what just happened but i promise if this occurs again i will past the code you would like to see.

scorp123
Level 8
Level 8
Posts: 2272
Joined: Sat Dec 02, 2006 4:19 pm
Location: Switzerland

Post by scorp123 »

lawngnome wrote:could the auto update have something to do with the cpu usage?
Yes, that could happen here and there, depending on what gets updated (e.g. the Kernel?) the system load might go up and the system may feel slow and sluggish. Especially when there is not plenty of free RAM (e.g. there is lots of other stuff running too during the update) the system may feel as if it has come to a halt. This shouldn't happen too often though ... if it does then there must be another problem somewhere else...

User avatar
alexander
Level 2
Level 2
Posts: 70
Joined: Sun Aug 26, 2007 9:44 pm

Post by alexander »

my CPU(s) run at near 100% constantly however thats because I run folding@home whenever the computer is on.

Is this bad for my CPU's health?

capchuckprice
Level 1
Level 1
Posts: 13
Joined: Tue Aug 14, 2007 4:00 am

Post by capchuckprice »

As long as your CPU is adequately cooled it does not hurt to soak up the idle cycles with background programs like your folding program. You won't "wear it out"...

User avatar
Jinnai
Level 2
Level 2
Posts: 76
Joined: Thu Sep 06, 2007 8:09 pm

Post by Jinnai »

Cverclocking, even when adequately cooled can though.

nelamvr6
Level 4
Level 4
Posts: 327
Joined: Sun Jul 08, 2007 8:14 pm
Location: New London, CT USA

Post by nelamvr6 »

alexander wrote:my CPU(s) run at near 100% constantly however thats because I run folding@home whenever the computer is on.

Is this bad for my CPU's health?
I've been folding 24/7 for YEARS, even on my laptops, and I haven't had problem 1.

So long as you're careful about adequate ventilation/cooling, there should be any problems.

nelamvr6
Level 4
Level 4
Posts: 327
Joined: Sun Jul 08, 2007 8:14 pm
Location: New London, CT USA

Post by nelamvr6 »

Jinnai wrote:Cverclocking, even when adequately cooled can though.
Amen!

In fact, that's how I discovered folding, it's a GREAT stress tester for your system.

I used to use Prime95, but I had OC's that would run Prime95 for hours that would crash on the folding client in a few minutes.

If your OC can fold overnight it's SOLID!

Post Reply

Return to “Newbie Questions”