Date: Tue, 4 Sep 2001 14:50:02 -0700 (PDT) From: .@babolo.ru To: freebsd-bugs@FreeBSD.org Subject: Re: bin/30310: top does not show CPU usage Message-ID: <200109042150.f84Lo2262989@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/30310; it has been noted by GNATS. From: .@babolo.ru To: andrey@novikov.com (Andrey Novikov) Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/30310: top does not show CPU usage Date: Wed, 5 Sep 2001 01:51:52 +0400 (MSD) Andrey Novikov writes: > > >Number: 30310 > >Category: bin > >Synopsis: top does not show CPU usage > >Confidential: no > >Severity: serious > >Priority: high > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Sep 04 06:10:01 PDT 2001 > >Closed-Date: > >Last-Modified: > >Originator: Andrey Novikov > >Release: FreeBSD 4.4-RC > >Organization: > >Environment: > FreeBSD spide.webclub.ru 4.4-RC FreeBSD 4.4-RC #2: Tue Sep 4 16:53:28 MSD 2001 novikov@spide.webclub.ru:/usr/src/sys/compile/SPIDE i386 > > >Description: > top utility allways show 0.00 in CPU states, both in summary and in per process stats: > > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle This is not a top utility problem. I saw sometime in in multiprocessor systems (possibly with one installed processor and free socket(s)) that timer 100 Hz (or may be my memory leak and it is 128Hz timer) stops. strange nulls on top is not the worst with this hardware. Usually timer throw interrupts some time (hours or days) after reboot then stops. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109042150.f84Lo2262989>