> > I'm seeing this as well, but only with PIII Xeon systems, not PII
> > Xeon. Every single timer interrupt on any CPU is accompanied by a NMI
> > and LOC increment on every CPU.
> >
> > CPU0 CPU1
> > 0: 146727 153389 IO-APIC-edge timer
> > [...]
> > NMI: 300035 300035
> > LOC: 300028 300028
>
> You mean that isn't supposed to happen?
>
> CPU0 CPU1
> 0: 8480192 7786028 IO-APIC-edge timer
> 1: 3 1 IO-APIC-edge keyboard
> 2: 0 0 XT-PIC cascade
> 8: 0 0 IO-APIC-edge rtc
> 13: 0 0 XT-PIC fpu
> 23: 188915 191259 IO-APIC-level eth0
> 28: 16 14 IO-APIC-level sym53c8xx
> 29: 33655 33665 IO-APIC-level sym53c8xx
> 30: 0 0 IO-APIC-level es1371
> NMI: 16266140 16266140
> LOC: 16266123 16266122
> ERR: 0
>
> This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
> chipset.
[wakko@gohan:/home/wakko] cat /proc/interrupts
CPU0 CPU1
0: 15276613 18358687 IO-APIC-edge timer
1: 391 455 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
4: 1 0 IO-APIC-edge serial
13: 1 0 XT-PIC fpu
14: 3013 2422 IO-APIC-edge ide0
16: 179450 191589 IO-APIC-level eth0
17: 22 23 IO-APIC-level aic7xxx
18: 17254 15655 IO-APIC-level es1371
19: 11 10 IO-APIC-level aic7xxx
NMI: 33635184 33635184
LOC: 33636726 33636725
ERR: 0
[wakko@gohan:/home/wakko] cat /proc/mtrr
I noticed it was a tad slow, but I figured it was the fact it was a netboot
machine. It's a dual ppro 200 192mb ram.
-- Lab tests show that use of micro$oft causes cancer in lab animals - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:12 EST