Re: also sound and lost cpu
Hi Ben,
It seems top always reports the following on the 2.6-0 test11 kernel
10:30am up 36 min, 4 users, load average: 0.85, 0.63, 0.48
77 processes: 74 sleeping, 3 running, 0 zombie, 0 stopped
CPU0 states: 26.0% user, 2.4% system, 0.0% nice, 71.0% idle
fscanf failed on /proc/stat for cpu 1
Mem: 771980K av, 398708K used, 373272K free, 0K shrd, 18908K buff
Swap:
Notice the "fscanf failed on /proc/stat for cpu 1"
I then catted /proc/stat and I can't really see anything wrong
[kbhend@base1 kbhend]$ cat /proc/stat
cpu 80507 0 9043 354838 7327 99 4
cpu0 43193 0 4267 175145 3232 15 0
cpu1 37313 0 4776 179692 4094 84 4
intr 387114 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 27 8 0 0 0 0 4086 24 73
287715 0 0 0 0 0 0 0 0 0 0 0 3 677 0 0 0 0 0 0 0 0 0 0 0 14 19955 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 82 74450 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0
ctxt 584779
btime 1070981597
processes 8360
procs_running 3
procs_blocked 0
I can actually add the LC field to top (using f and then selecting the last
processor used field) and it seems to show both processors humming along
nicely.
So maybe just some wierd format change in the output used in /proc/stat that
is causing "top" to be confused?
Kevin
On Monday 08 December 2003 19:38, Kevin B. Hendricks wrote:
> Hi Ben,
>
> I also seem to be having sound troubles with 2.6.0 that do not happen with
> 2.4.23. I have buyilt 2.6.0-test11 with i2c-keywest built in and not as a
> module so I can't try the rmmod trick.
>
> I will rebuild and revert to keeping it a module.
>
> The real issue is that I have run into one of my 2 cpu's literally
> disappearing according to "top" and to its slower performance.
>
> This has never happened with 2.4.XX. Has anyone else reported anything
> similar on their SMP machines.
>
> If it matters, this is with HIGHMEM but without distributing irq/interrupts
> to every CPU.
>
> I have since booted back into 2.4.23 and all seems fine again.
>
> Kevin
Reply to: