From owner-freebsd-questions Fri Aug 30 7:31:35 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A158F37B400 for ; Fri, 30 Aug 2002 07:31:32 -0700 (PDT) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89E0A43E65 for ; Fri, 30 Aug 2002 07:31:31 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.5/8.12.5) with ESMTP id g7UEVPNR003809; Fri, 30 Aug 2002 10:31:25 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.5/8.12.5/Submit) with ESMTP id g7UEVOkL003806; Fri, 30 Aug 2002 10:31:24 -0400 (EDT) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Fri, 30 Aug 2002 10:31:24 -0400 (EDT) From: Kenneth Culver To: Joseph Lephan Cc: freebsd-questions@FreeBSD.ORG Subject: Re: freebsd not correctly monitoring cpu usage In-Reply-To: <20020829230337.A35047@houston.rr.com> Message-ID: <20020830102919.H3800-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > nope, top didn't register it either: 0.0% for user/nice/system/interrupt/idle > > > > > some load monitors only work on linux. i'd expect them to work if > > you installed them from ports, but you don't say if you did or not. > > both gkrellm and wmaker were installed from ports. I thinking about trying to > compile from source, but i don't know how that will turn out > > > > > ps - while writing the above 3 lines, i installed gkrellm on my > > freebsd 4.5 machine and it worked fine! > > Darn IT!!! :o) > > The only time I've ever seen the behavior you are seeing is on laptops or other machines with broken statclocks. The way I fixed it was by adding the following line to my kernel config: device apm0 at nexus? flags 0x20 The 0x20 supposedly works around the broken statclock somehow... allowing at least somewhat accurate cpu usages to be reported (they aren't fully accurate because you need both clocks to report cpu stats accurately) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message