I encountered the same problem and found the bugreport already here. It seems to be just /proc/interrupts parsing problem. Attached is also my /proc/interrputs for testing.
-- Meelis Roos ([EMAIL PROTECTED])
CPU0 CPU1 0: 58 3141 IO-APIC-edge timer 1: 225 21942 IO-APIC-edge i8042 6: 0 5 IO-APIC-edge floppy 7: 1 0 IO-APIC-edge 8: 0 1 IO-APIC-edge rtc0 9: 2 216 IO-APIC-fasteoi acpi 12: 2688 207118 IO-APIC-edge i8042 14: 68605 5627986 IO-APIC-edge pata_amd 15: 0 0 IO-APIC-edge pata_amd 16: 137448 46748361 IO-APIC-fasteoi firewire_ohci, nvidia 20: 112188 17471493 IO-APIC-fasteoi ehci_hcd:usb1, HDA Intel 21: 21645 4022027 IO-APIC-fasteoi sata_nv, ohci_hcd:usb2 22: 0 0 IO-APIC-fasteoi sata_nv 23: 103103 10856183 IO-APIC-fasteoi sata_nv 1275: 4895879 389509638 PCI-MSI-edge eth0 NMI: 0 0 Non-maskable interrupts LOC: 221034884 476135388 Local timer interrupts RES: 130955231 43041156 Rescheduling interrupts CAL: 8617844 8533923 function call interrupts TLB: 12059 9278 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts SPU: 0 0 Spurious interrupts ERR: 1
