From owner-freebsd-current@FreeBSD.ORG  Sun Jan 11 10:04:18 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8ABAA16A4CE
	for <freebsd-current@freebsd.org>;
	Sun, 11 Jan 2004 10:04:18 -0800 (PST)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4474543D48
	for <freebsd-current@freebsd.org>;
	Sun, 11 Jan 2004 10:04:15 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa45366@salmon>; 11 Jan 2004 18:04:14 +0000 (GMT)
Date: Sun, 11 Jan 2004 18:04:12 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Scott W <wegster@mindcore.net>
Message-ID: <20040111180412.GA54067@walton.maths.tcd.ie>
References: <200401110114.i0B1Eb3d013350@f1.masterplan.org>
	<40017EDB.4030801@mindcore.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40017EDB.4030801@mindcore.net>
User-Agent: Mutt/1.5.3i
Sender: dwmalone@maths.tcd.ie
cc: Jason George <bsdlists@masterplan.org>
cc: freebsd-current@freebsd.org
Subject: Re: `top` reports all CPU states as 0% on i386
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jan 2004 18:04:18 -0000

On Sun, Jan 11, 2004 at 11:50:35AM -0500, Scott W wrote:
> Not sure this helps in any immediate fashion, but another data point....

I think this problem is usually caused by one of the clock interrupts
stopping. Checking the output of "vmstat -i" can confirm this - check
for:

clk irq0               1044322763        100
rtc irq8               1352668148        129

The rate for the first one should 100 (Or possibly HZ, if you have
adjusted HZ). The rate of the second should be about 128, unless
things have got confused.

	David.