From owner-freebsd-current  Wed Apr  9 12:23:00 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA10284
          for current-outgoing; Wed, 9 Apr 1997 12:23:00 -0700 (PDT)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10266
          for <freebsd-current@freebsd.org>; Wed, 9 Apr 1997 12:22:55 -0700 (PDT)
Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id PAA20011; Wed, 9 Apr 1997 15:22:21 -0400 (EDT)
Message-Id: <199704091922.PAA20011@whizzo.transsys.com>
To: Brian Tao <taob@nbc.netcom.ca>
cc: Frank Chen Hsiung Chan <frankch@waru.life.nthu.edu.tw>,
        FREEBSD-CURRENT-L <freebsd-current@freebsd.org>
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: XFree86 3.2 causes constant 1.0 load average? 
References: <Pine.GSO.3.95.970409134504.18937c-100000@tor-adm1.nbc.netcom.ca> 
In-reply-to: Your message of "Wed, 09 Apr 1997 13:46:52 EDT."
             <Pine.GSO.3.95.970409134504.18937c-100000@tor-adm1.nbc.netcom.ca> 
Date: Wed, 09 Apr 1997 15:22:21 -0400
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Why not "ktrace" the process to see what it's doing?  I've noticed a similar
problem with an X11 application (fxtv, which puts a window frame up on the
display and waits for events while the kernel driver arranged the video image
to be copied into the frame buffer).  When I ktrace'ed it, it noticed it doing
a whole bunch 'o FIONREAD ioctl's, just as hard as it could.  I've not 
investigated any further yet, but something like this would get you pointed
in the right direction.

louie