I have the similar problem on ASUS P2B-D/P2B-DS (SMP) but not only top %s
and on the top without parameters. After starting system top work correctly
but after some minutes (~2-5) top write zeros.
>From two equal computers only one have this problem. BIOS upgrade was not
resolve this problem.
On 15-Mar-2000 Nathan Sheeley wrote:
>
> As of roughly Mon Mar 6 19:37:1 CST 2000 /usr/bin/top doesn't show the
> correct (or any) percentage CPU usage. (example below.) A minor issue I
> know, just wanted to point it out if its part of a larger issue.
>
> Since upgrading to -current I've noticed:
> o sound now works with my es1371 sb128 pci card, where it didn't no
> matter what I tried in 3.4 stable.
> o things that allocate? shared memory (Linux CivCTP, wine) now work
> when I use a SMP kernel (I have a Abit BP6 w/2 433 Celerons)
> o my machine locks up after about 20 hours of uptime.
>
> Obviously the last one is quite annoying, but I haven't been able to
> get any info yet on why the crashes happen (I have a dumpdev now, so
> it refuses to crash ;)
>
> Nate
>
> last pid: 49105; load averages: 2.06, 1.63, 1.28
> up 1+04:43:59 00:24:42
> 30 processes: 3 running, 27 sleeping
> CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0%
> idle
> Mem: 51M Active, 7520K Inact, 18M Wired, 760K Cache, 10M Buf, 47M Free
> Swap: 256M Total, 1560K Used, 254M Free
>
> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
> 49045 nobody 30 1 14676K 14340K RUN 1 3:18 0.00% 0.00%
> setiathome
> 49048 nobody 30 1 14676K 14340K CPU0 0 3:12 0.00% 0.00%
> setiathome
> 49070 nsheeley 2 0 49372K 42720K select 1 0:04 0.00% 0.00%
> XF86_SVGA
> 199 root 10 0 928K 160K nanslp 1 0:01 0.00% 0.00% cron
> 160 root 2 0 872K 252K select 1 0:01 0.00% 0.00% syslogd
> 49076 nsheeley 10 0 3272K 1984K nanslp 1 0:01 0.00% 0.00% xearth
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
Tolyar.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
