Date: Mon, 20 Sep 1999 15:32:50 -0700 From: "Kelsey Cummings" <kc@neteze.com> To: "Christopher Michaels" <ChrisMic@clientlogic.com>, "'John E. Hein'" <jhein@timing.com> Cc: <freebsd-questions@freebsd.org> Subject: Re: CPU times not displaying in 'top' Message-ID: <002d01bf03b8$128fe830$33f9c9d0@neteze.com> References: <6C37EE640B78D2118D2F00A0C90FCB4401105C7B@site2s1>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks... (apm is disabled..) ----------------------------------------------------------------- Kelsey Cummings System Administrator NetEase, Inc. kc@neteze.com ----------------------------------------------------------------- ----- Original Message ----- From: Christopher Michaels <ChrisMic@clientlogic.com> To: 'John E. Hein' <jhein@timing.com>; Kelsey Cummings <kc@neteze.com> Cc: <freebsd-questions@freebsd.org> Sent: Monday, September 20, 1999 2:43 PM Subject: RE: CPU times not displaying in 'top' > For the record I thought this was something that was addresses about a month > or 2 ago. I don't remember the solution since I don't run an SMP kernel > myself. I believe it had something to do with APM being enabled in the > kernel config. > > Take a look through the questions and stable mailing list archives and I > think you'll find your solution. > > -Chris > > > -----Original Message----- > > From: John E. Hein [SMTP:jhein@timing.com] > > Sent: Monday, September 20, 1999 5:22 PM > > To: Kelsey Cummings > > Cc: freebsd-questions@freebsd.org > > Subject: CPU times not displaying in 'top' > > > > Kelsey Cummings wrote at 13:30 -0700 on Sep 20: > > > I recently noticed that the cpu times on my server are not displayed > > under > > > top. 'uptime' reports the average cpu times. I'm running 3.2-release > > with > > > and SMP kernel (dual pII-450 on a ASUS p2bs(?)) Is this something that > > I > > > should be concerned about? What's broken? > > [top output snipped] > > > > FWIW, I get the same symptoms (3.2-STABLE dual CPU). 'ps' and 'vmstat' > > both > > behave the same way (they report 0 % CPU usage for all processes even > > under > > heavy load). > > > > Note, I tried it after rebooting nearly 3 weeks ago, and it was not > > working. Then I tried it when I received your email just to double > > check. It was working! So I ran 'xosview' (are you running that, > > too?), and it was working fine for about 10 minutes. Then I got the > > following error message and all indicators (top, ps, vmstat) resumed > > their bogus '0% CPU usage' behavior. > > > > Warning: CPUMeter meter had a zero total field! Would have caused a > > div-by-zero exception. > > Warning: the CPU tick counters are not changing. This could > > be due to running a kernel besides /netbsd (or the equivalent for > > FreeBSD). > > If this is the case, re-run xosview with the -N kernel-name option. > > If not, then this is a bug. Please send a message to > > bgrayson@ece.utexas.edu, in addition to any send-pr bug reports > > (or in lieu of -- it ought to get fixed faster if you contact me > > directly). Thanks! > > > > For those that don't know, xosview is a GUI CPU/etc. meter (see > > /usr/ports/sysutils/xosview). > > > > > > % uname -s -r -m > > FreeBSD 3.2-STABLE i386 > > > > % ps auwx | awk '{print $3}' | sort -u > > %CPU > > 0.0 > > > > % vmstat 3 > > procs memory page disks faults cpu > > r b w avm fre flt re pi po fr sr da0 da1 fd0 in sy cs us > > sy id > > 1 2 0 13748 10968 10 0 0 0 10 9 0 0 0 146 21 98 0 > > 2 98 > > 1 1 0 15116 9704 2 0 0 0 0 0 0 59 0 419 35 192 0 > > 0 0 > > 0 1 0 15620 8552 1 0 0 0 0 0 0 66 0 505 40 242 0 > > 0 0 > > 0 1 0 18628 13636 104 0 0 0 65 528 0 86 0 556 195 252 0 > > 0 0 > > 1 1 0 18628 12312 1 0 0 0 1 0 0 64 0 441 93 207 0 > > 0 0 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002d01bf03b8$128fe830$33f9c9d0>