From owner-freebsd-current@FreeBSD.ORG  Sun Jan 11 17:32:49 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 22CFB16A4CE
	for <freebsd-current@freebsd.org>;
	Sun, 11 Jan 2004 17:32:49 -0800 (PST)
Received: from f1.masterplan.org (h68-144-20-87.cg.shawcable.net
	[68.144.20.87])	by mx1.FreeBSD.org (Postfix) with ESMTP id 1B39543D49
	for <freebsd-current@freebsd.org>;
	Sun, 11 Jan 2004 17:32:47 -0800 (PST)
	(envelope-from bsdlists@masterplan.org)
Received: from axe (laptop [192.168.4.9])
	by f1.masterplan.org (8.12.10/8.12.10) with SMTP id i0C1WipO000427
	for <freebsd-current@freebsd.org>;
	Sun, 11 Jan 2004 18:32:44 -0700 (MST)
	(envelope-from bsdlists@masterplan.org)
Message-Id: <200401120132.i0C1WipO000427@f1.masterplan.org>
From: bsdlists@masterplan.org (Jason George)
To: freebsd-current@freebsd.org
Date: Mon, 12 Jan 2004 01:32:44 GMT
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	f1.masterplan.org
X-Mailman-Approved-At: Sun, 11 Jan 2004 18:27:02 -0800
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: Mon, 12 Jan 2004 01:32:49 -0000




>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.

Yikes!  I think my RTC has left the building!

> vmstat -i
interrupt                          total       rate
irq1: atkbd0                           1          0
irq6: fdc0                             4          0
irq10: fxp0 xl0                    86393          1
irq11: atapci0                    255394          3
irq13: npx0                            1          0
irq0: clk                        8087632         99
Total                            8429425        103
>


Another point of interest is that about 8 months ago, I added 
kern.timecounter.hardware=i8254 to /etc/sysctl.conf because the system clock 
was going insane - it was counting off an hour of system time in the matter 
of a minute or so of wristwatch time.

--Jason