From owner-freebsd-current  Sun Apr  6 21:31:51 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA18076
          for current-outgoing; Sun, 6 Apr 1997 21:31:51 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18042
          for <freebsd-current@freebsd.org>; Sun, 6 Apr 1997 21:31:46 -0700 (PDT)
Received: from waru.life.nthu.edu.tw (root@waru.feminism.net [140.114.98.107])
          by who.cdrom.com (8.8.5/8.6.11) with ESMTP id RAA27461
          for <freebsd-current@freebsd.org>; Sun, 6 Apr 1997 17:11:47 -0700 (PDT)
Received: from waru.life.nthu.edu.tw (frankch@waru.feminism.net [140.114.98.107])
	by waru.life.nthu.edu.tw (8.8.5/8.8.5) with SMTP id IAA05209;
	Mon, 7 Apr 1997 08:13:02 +0800 (CST)
Date: Mon, 7 Apr 1997 08:13:02 +0800 (CST)
From: Frank Chen Hsiung Chan <frankch@waru.life.nthu.edu.tw>
To: Brian Tao <taob@risc.org>
cc: FREEBSD-CURRENT-L <freebsd-current@freebsd.org>
Subject: Re: XFree86 3.2 causes constant 1.0 load average?
In-Reply-To: <Pine.BSF.3.95.970406120732.13146E-100000@alpha.risc.org>
Message-ID: <Pine.BSF.3.95q.970407081125.5202A-100000@waru.life.nthu.edu.tw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 6 Apr 1997, Brian Tao wrote:
>     Has anyone else noticed that XFree86 3.2 will in many cases (but
> not always) cause a 2.2 or 3.0 system to report a load average of at
> least 1.0?  ps/top both indicate little or no CPU activity, but the
> load average does not fall below 1.0 unless I kill off X.

   We had this problem here. We then found that the asclock is
   responsible for this. Try not running asclock and/or other 
   asstuff, that might help.

--frank