Re: uptime is too high. Is it normal?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ralf,
Here is the result:

/usr/local/bin # ps -aux
  PID  Uid     VmSize Stat Command
    1 root        412 S   init
    2 root            SWN [ksoftirqd/0]
    3 root            SW< [events/0]
    4 root            SW< [khelper]
    5 root            SW< [kthread]
    6 root            SW< [kblockd/0]
    9 root            SW  [khubd]
   36 root            SW  [pdflush]
   37 root            SW  [pdflush]
   39 root            SW< [aio/0]
   38 root            SW  [kswapd0]
  645 root            SW  [645]
  646 root            DW  [646]
  647 root            DW  [647]
  648 root            SW  [648]
  649 root            SW  [mtdblockd]
  666 root            SW  [kjournald]
  680 root        380 S   /sbin/syslogd -p /tmp/.log -n -m 0
  681 root        348 S   /sbin/klogd -n
  753 root        400 S   inetd
  793 root        572 S   -sh
  794 root        416 S   init
  811 root        416 S   init
  822 root        416 S   init
  980 root            SW< [rpciod/0]
 1015 root        396 R   ps -aux
/usr/local/bin # uptime
 00:19:29 up 19 min, load average: 2.00, 1.95, 1.41

The uptime value keeps on going higher and higher.
It seems that both 646 & 647 process has the same parent "1".
Their "utime" are "0".

Thanks and regards,
Colin


----- Original Message ----- 
From: "Ralf Baechle" <ralf@xxxxxxxxxxxxxx>
To: "colin" <colin@xxxxxxxxxxxxxx>
Cc: <linux-mips@xxxxxxxxxxxxxx>
Sent: Tuesday, March 21, 2006 8:52 PM
Subject: Re: uptime is too high. Is it normal?


> On Tue, Mar 21, 2006 at 08:39:08PM +0800, colin wrote:
>
> > Hi all,
> > We use MIPS Linux+uClibc0.9.28+busybox 1.1.0 on our machine.
> > After use "uptime" to get the loading of device, it shows:
> >     03:50:05 up  3:50, load average: 2.00, 2.00, 2.00
> > Is it normal? It seems too high because my PC Linux has a much lower
value:
> >     20:38:31 up 12 days,  5:11,  5 users,  load average: 0.04, 0.01,
0.00
>
> Well, check with ps what is causing the load.  Look for processes in
> either 'D' or 'R' state.
>
>   Ralf



[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux