On 27-Mar-01 David Wolfskill wrote:
>>Date: Tue, 27 Mar 2001 08:33:10 -0800 (PST)
>>From: John Baldwin <[EMAIL PROTECTED]>
>
>>Not one that I've seen:
>
>> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
>> 11 root -16 0 0K 0K CPU0 0 79.5H 49.37% 49.37% idle:
>> cpu0
>> 10 root -16 0 0K 0K RUN 1 79.4H 48.19% 48.19% idle:
>> cpu1
>> 13 root -48 -167 0K 0K WAIT 0 62:53 0.00% 0.00% swi6:
>> tty:s
>> 15 root 76 0 0K 0K sleep 0 6:07 0.00% 0.00% random
>> 5 root 20 0 0K 0K syncer 1 2:47 0.00% 0.00% syncer
>> 20 root -68 -187 0K 0K WAIT 1 1:18 0.00% 0.00% irq18:
>> fxp0
>> 19 root -64 -183 0K 0K WAIT 0 0:53 0.00% 0.00% irq16:
>> ahc0
>> 12 root -44 -163 0K 0K WAIT 0 0:52 0.00% 0.00% swi1: net
>> 18 root -36 -155 0K 0K WAIT 1 0:49 0.00% 0.00% swi3:
>> cambi
>> 4 root -16 0 0K 0K psleep 0 0:41 0.00% 0.00% bufdaemon
>> 283 root 4 0 552K 388K select 0 0:10 0.00% 0.00% dhclient
>
>>If you run 'top -S' does all your time show up in the idle processes like it
>>does here?
>
> Hmm... mine loks like that (modulo #CPUs), except when I'm actually
> making it do some work (re-building the kernel, in this case). What I
> see ("top -S") looks like:
>
> last pid: 9546; load averages: 0.97, 0.64, 0.30 up 0+00:08:32
> 08:51:47
> 77 processes: 3 running, 57 sleeping, 2 zombie, 15 waiting
> CPU states: 91.1% user, 0.0% nice, 5.4% system, 0.4% interrupt, 3.1% idle
This is probably right..
I don't know why you are seeing such weirdness however. Is your world and
kernel out of sync. It's a nice (mis)feature now that if items in the middle
of kinfo_proc change size it still tries to use the misordered data rather than
complaining about it like it used to. :-P See my other e-mail where top on my
laptop doles out time to userland tasks ok.
> I confess a degree of skepticism.... :-}
I agree.
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
