From owner-freebsd-questions@FreeBSD.ORG Mon Jun 16 10:20:07 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB5FC37B401 for ; Mon, 16 Jun 2003 10:20:07 -0700 (PDT) Received: from out004.verizon.net (out004pub.verizon.net [206.46.170.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1FCE43FA3 for ; Mon, 16 Jun 2003 10:20:06 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out004.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030616172006.JYNN246.out004.verizon.net@mac.com>; Mon, 16 Jun 2003 12:20:06 -0500 Message-ID: <3EEDFC3F.20703@mac.com> Date: Mon, 16 Jun 2003 13:19:59 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stijn Hoop References: <20030616141153.GH49234@pcwin002.win.tue.nl> In-Reply-To: <20030616141153.GH49234@pcwin002.win.tue.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [141.149.47.46] at Mon, 16 Jun 2003 12:20:05 -0500 cc: freebsd-questions@freebsd.org Subject: Re: got load > 1 but no CPU state is showing? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2003 17:20:08 -0000 Stijn Hoop wrote: > On a lightly loaded server top is misbehaving: it continuously shows all > CPU states at 0.0% yet my load varies from 0.50 to about 3. Is there > any explanation for this? Maybe. :-) I was going to say that on fast machines, it's not unusual for processes which start up and then finish quickly to go away before top "sees" them, but you still see the effect in the aggregate system load. However, that doesn't explain this line: > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Clutching at straws, maybe top can't read /dev/kmem or something? Try doing a "MAKEDEV all" in /dev... -Chuck