I, too, see this all the time, and have since I upgraded to 3.0 (same machine,
have upgraded incrementally to 3.1, 3.2, 3.3, 4.0, 4.1, 4.2 (all -STABLEs)),
and have seen this the whole time.  Never tracked it down, either...

(Just another data point)

My machine: PII/266, 128MB memory, P2L97 motherboard (everything else has
changed at one time or another)

--David Bushong

On Sat, Mar 10, 2001 at 05:27:22AM -0800, Mike Harding wrote:
> 
> I have seen this behavior a number of times over the years, but never
> tracked it down.  I even looked at the kernel code which computed the
> load to see if I could identify anything obvious.
> 
> I have noticed that when this happes, the load is basically a
> completely stable value of 1.0 or very close to it, almost like it is
> in a locally stable state.  Didn't look for zombies though - I use
> junkbuster and it always keeps a few zombies around because the main
> spawn loop is screwy.  (grrr).
> 
> - Mike Harding
> 
>    Date: Sat, 10 Mar 2001 23:58:51 +1100 (EST)
>    From: Bruce Evans <[EMAIL PROTECTED]>
>    X-Sender: [EMAIL PROTECTED]
>    Cc: Mikhail Teterin <[EMAIL PROTECTED]>
>    Content-Type: TEXT/PLAIN; charset=US-ASCII
>    Sender: [EMAIL PROTECTED]
>    X-Loop: FreeBSD.ORG
>    Precedence: bulk
> 
>    On Fri, 9 Mar 2001, Will Andrews wrote:
> 
>    > On Fri, Mar 09, 2001 at 10:39:53AM -0500, Mikhail Teterin wrote:
>    > > I was running a single instance of SETI@Home, when I observed the load
>    > > of 2. I stopped seti and the load went down to one. It stays there for
>    > > about 20 hours already. The machine is idle:
> 
>    > top(1) doesn't show all stats relevant to the load average.  Check
>    > vmstat/systat/iostat/netstat/etc.
> 
>    Perhaps it is the entropy harvester reaping itself ;-).
> 
>    > Besides, the load average is a
>    > worthless metric if you ask me.
> 
>    Erm, it is a fundamental part of the scheduler.  The scheduler is b0rked,
>    but not that part of it.
> 
>    Bruce
> 
> 
>    To Unsubscribe: send mail to [EMAIL PROTECTED]
>    with "unsubscribe freebsd-stable" in the body of the message
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to