From owner-freebsd-current Mon Sep 11 2:26:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 1637A37B422 for ; Mon, 11 Sep 2000 02:26:42 -0700 (PDT) Received: (from netch@localhost) by segfault.kiev.ua (8) id MKC21646; Mon, 11 Sep 2000 12:26:15 +0300 (EEST) (envelope-from netch) Date: Mon, 11 Sep 2000 12:26:14 +0300 From: Valentin Nechayev To: Bruce Evans Cc: freebsd-current@freebsd.org Subject: Re: load average is 1 when no processes active; etc. Message-ID: <20000911122614.A21310@netch.kiev.ua> Reply-To: netch@segfault.kiev.ua References: <20000910153643.A799@nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Mon, Sep 11, 2000 at 03:09:02AM +0000 X-42: On Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Bruce Evans! Mon, Sep 11, 2000 at 03:09:02, bde wrote about "Re: load average is 1 when no processes active; etc.": > > `top -I' output: > > > > ==={ > > last pid: 811; load averages: 1.01, 0.97, 0.67 up 0+00:16:12 23:26:26 > > This is because the idle process is always running (see "ps lax" outout). > Perhaps the bug is that top doesn't show the idle process or other interesting > kernel processes like the new interrupt processes. top does nothing to determine LA except getting sysctl "vm.loadavg", isn't it? ("uptime" and "w" says the same avenrun/LA values.) Imho, idle process should not be determined as always running, and idle process state should be fixed. > > IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled > > microuptime() went backwards (1.3891137 -> 0.596214) > > microuptime() went backwards (1.3891137 -> 0.596655) > > ... > > I get these at boot time on one machine but not on another very similar > machine, and often after messing around with ddb. TSC timecounter in > all cases. I think they are not a serious problem or related to old > timecounter bugs, but they may be related to old bugs setting `switchtime'. What information of my hardware should be reported additionally? /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message