Date: Sun, 6 Apr 1997 19:10:31 -0400 (EDT) From: Brian Tao <taob@risc.org> To: Justin Wolf <jjwolf@bleeding.com> Cc: FREEBSD-CURRENT-L <freebsd-current@freebsd.org> Subject: RE: XFree86 3.2 causes constant 1.0 load average? Message-ID: <Pine.BSF.3.95.970406190800.13146J-100000@alpha.risc.org> In-Reply-To: <01BC426E.D624C120@crimson>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Apr 1997, Justin Wolf wrote:
>
> To expand on this a little... what would cause 2.2 to report 1.0
> loadavgs when there's nothing going on? I've noticed this happening
> after killing threads and such and rebooting is the only way to get
> it back to 0. Is this a bug under 2.2? (Although I first noticed it
> after running X, it's now happening even without.)
I'm always in X, so I don't notice if the problem persists without
it, but it seems to come and go on its own under X. Right now, for
example, the load average is at a more sensible level, but I'm running
the same application mix as before. I think I may have run xlock a
couple of times and acroread in between.
last pid: 14108; load averages: 0.17, 0.32, 0.60 19:09:38
52 processes: 4 running, 48 sleeping
CPU states: 2.2% user, 0.0% nice, 1.5% system, 0.0% interrupt, 96.4% idle
Mem: 30M Active, 8856K Inact, 15M Wired, 7372K Cache, 7602K Buf, 1128K Free
Swap: 128M Total, 21M Used, 107M Free, 16% Inuse
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
8121 root 28 0 7788K 16968K RUN 851:41 0.99% 0.99% XF86_Mach64
14108 root 28 0 324K 804K RUN 0:00 3.36% 0.61% top
14099 taob 28 0 564K 1936K RUN 0:01 0.11% 0.11% xterm
8182 taob 28 0 3140K 800K RUN 0:31 0.04% 0.04% screen-3.7.1
12299 taob 18 0 1140K 1620K pause 21:01 0.00% 0.00% xearth
[...]
--
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970406190800.13146J-100000>