All of lore.kernel.org
 help / color / mirror / Atom feed
From: "colin" <colin@realtek.com.tw>
To: "Ralf Baechle" <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: uptime is too high. Is it normal?
Date: Tue, 21 Mar 2006 21:14:06 +0800	[thread overview]
Message-ID: <00a101c64ce9$554b3180$106215ac@realtek.com.tw> (raw)
In-Reply-To: 20060321125255.GA8779@linux-mips.org


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@linux-mips.org>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-mips@linux-mips.org>
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

WARNING: multiple messages have this Message-ID (diff)
From: "colin" <colin@realtek.com.tw>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: uptime is too high. Is it normal?
Date: Tue, 21 Mar 2006 21:14:06 +0800	[thread overview]
Message-ID: <00a101c64ce9$554b3180$106215ac@realtek.com.tw> (raw)
Message-ID: <20060321131406.mhCO6RNXolIYbzMsf8qK1viuX-xPeCGSU4wNtg0hSQk@z> (raw)
In-Reply-To: 20060321125255.GA8779@linux-mips.org


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@linux-mips.org>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-mips@linux-mips.org>
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

  reply	other threads:[~2006-03-21 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 12:39 uptime is too high. Is it normal? colin
2006-03-21 12:39 ` colin
2006-03-21 12:52 ` Ralf Baechle
2006-03-21 13:14   ` colin [this message]
2006-03-21 13:14     ` colin
2006-03-21 13:36     ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00a101c64ce9$554b3180$106215ac@realtek.com.tw' \
    --to=colin@realtek.com.tw \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.