bin/60385: vmstat/iostat/top all fail to report CPU usage (still in 5.3R)

[Dima Dorfman]

The following reply was made to PR bin/60385; it has been noted by GNATS.

From: Dima Dorfman <dd at freebsd.org>
To: freebsd-gnats-submit at freebsd.org
Cc: Jeff Behl <jbehl at fastclick.com>, Thomas Novin <thnov at xyz.pp.se>
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.