Hal Burgiss wrote:
>
> First spike CPU0:
>
> PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> 654 root 12 0 65068 52M 2664 S 0 21.9 41.5 125:22 X
> 708 hal 7 0 348 284 228 S 0 11.2 0.2 28:16 wmnet
>
> A few seconds later CPU1:
>
> PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> 654 root 15 0 65068 52M 2664 S 0 17.5 41.5 125:29 X
> 708 hal 12 0 348 284 228 S 0 12.1 0.2 28:17 wmnet
>
> A few seconds later now -- between spikes (ie normal):
>
> PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> 703 hal 14 0 428 260 200 S 0 1.3 0.2 59:15 wmsysmon
> 17541 hal 12 0 1036 1036 820 R 0 1.1 0.8 0:02 top
> 654 root 18 0 65068 52M 2664 S 0 0.3 41.5 125:30 X
>
> This was actually a while back with 2.2.14pre IIRC. BP6 with QQ BIOS
> (now stable!).
>
> --
> Hal B
> [EMAIL PROTECTED]
I have observed the same spikes (mb Gigabyte 586DX 2x200Mhz MMX & Voodoo
3 & SB AWE 32 & 96 Mb RAM & ...) as we can see above and in my opinion
it's seemd to be some kind of feedback. At a time something uses more
cpu, xosview request X to draw so does it the other monitoring apps, in
theory it should be the same as with no load, but with gkrellm you can
see saw theeth, and as it's said the cpu "hog" is X, but could it be
related to the Voodoo 3??
--
Jorge Nerin
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
