From owner-freebsd-bugs@FreeBSD.ORG Fri Nov 19 00:30:32 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA35316A4CE for ; Fri, 19 Nov 2004 00:30:32 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B79A243D53 for ; Fri, 19 Nov 2004 00:30:32 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iAJ0UWLs055531 for ; Fri, 19 Nov 2004 00:30:32 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iAJ0UWNO055509; Fri, 19 Nov 2004 00:30:32 GMT (envelope-from gnats) Date: Fri, 19 Nov 2004 00:30:32 GMT Message-Id: <200411190030.iAJ0UWNO055509@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Dima Dorfman Subject: Re: bin/60385: vmstat/iostat/top all fail to report CPU usage (still in 5.3R) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dima Dorfman List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 00:30:32 -0000 The following reply was made to PR bin/60385; it has been noted by GNATS. From: Dima Dorfman To: freebsd-gnats-submit@freebsd.org Cc: Jeff Behl , Thomas Novin Subject: Re: bin/60385: vmstat/iostat/top all fail to report CPU usage (still in 5.3R) Date: Fri, 19 Nov 2004 00:22:01 +0000 Based on Thomas's report that the same system disk works in another machine, this sounds like a problem with support for certain kind of hardware. I can't reproduce it on any of my machines here. If you have a system that has this problem, the following output would be useful to help diagnose this. These sysctls: # sysctl kern.clockrate # sysctl kern.timecounter # sysctl vm.loadavg dmesg information about the timecounters: # fgrep Timecounter /var/run/dmesg.boot Also, a few samples of this sysctl at 5 second intervals: # sysctl kern.cp_time And just as a sanity check, try something like this: # /usr/bin/time ls -R > /dev/null and see whether the output is non-zero (but make sure that the command takes long enough to accrue some time!). uname output and a summary of the hardware in question (i386/amd64, SMP, HT) would be helpful to go with the above output.