Bug: <NULL>-edge in /proc/interrupts

["Marko Vrh" <marko.vrh@gmail.com>]

On x86_64, kernel 2.6.19-rc1-git11 (but it's been like that since -rc1,
i think), /proc/interrupts shows:

 0:   25980801    <NULL>-edge     timer

It used to be Local-APIC-edge. The local APIC is used due to a chipset bug
(ATI RS480/SB400).

Regards.
--Marko

(Please cc: me in replies, i'm not on the list)

/proc/interrupts in full:
          CPU0
 0:   25980801    <NULL>-edge     timer
 1:      32668   IO-APIC-edge     i8042
 8:          0   IO-APIC-edge     rtc
12:      27763   IO-APIC-edge     i8042
14:     640128   IO-APIC-edge     libata
15:         23   IO-APIC-edge     libata
17:       8761   IO-APIC-fasteoi  ATI IXP
19:      74283   IO-APIC-fasteoi  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
20:          1   IO-APIC-fasteoi  yenta
21:      96860   IO-APIC-fasteoi  acpi
23:    7966724   IO-APIC-fasteoi  eth0
NMI:       1823
LOC:   25976459
ERR:        234

Reason for using local APIC:

..MP-BIOS bug: 8254 timer not connected to IO-APIC
Using local APIC timer interrupts.
result 12469249
Detected 12.469 MHz APIC timer.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/