partha chowdhury wrote:
Sep 19 13:13:02 station2 kernel: irq 50: nobody cared (try booting
with the "irqpoll" option)
cat /proc/interrupts and see what it says(post output to the list if you want).
One thing to try, if something is sharing irq50 with another device, if that device is an expansion card then try moving that expansion card to another slot in the system.
For the system I am on for reference:
CPU0 CPU1 CPU2 CPU3 0: 349449438 97827289 129150703 1324419 IO-APIC-edge timer 4: 22709754 0 0 0 IO-APIC-edge serial 8: 572455673 15473535 564615318 27739670 IO-APIC-edge rtc 9: 1 0 0 0 IO-APIC-level acpi 15: 74017 49259 29528511 0 IO-APIC-edge ide1 50: 13430140 0 12041824 0 IO-APIC-level eth2 74: 7857068 0 0 0 IO-APIC-level Intel 82801DB-ICH4 169: 142038093 0 0 0 IO-APIC-level uhci_hcd:usb1, nvidia 177: 2719957 0 0 0 IO-APIC-level uhci_hcd:usb2 185: 0 0 0 0 IO-APIC-level uhci_hcd:usb3 193: 65184 0 4501500 0 IO-APIC-level ehci_hcd:usb4, ohci_hcd:usb7 201: 13311819 94167 14802720 262062 IO-APIC-level 3w-xxxx 209: 19049441 916146 11652498 250590 IO-APIC-level eth0 217: 1612506 0 0 0 IO-APIC-level ehci_hcd:usb5 225: 3263237 0 0 0 IO-APIC-level ohci_hcd:usb6 233: 1810468 3618 29330 424 IO-APIC-level eth1 NMI: 0 0 0 0 LOC: 577787080 577787079 577787078 577787077 ERR: 0 MIS: 0
Nothing sharing irq 50 on this machine, though irq 169 is being shared by both my Nvidia video card and a 4-port USB expansion card.
The kernel source code describes the error as this:
* If 99,900 of the previous 100,000 interrupts have not been handled * then assume that the IRQ is stuck in some manner. Drop a diagnostic * and try to turn the IRQ off. * * (The other 100-of-100,000 interrupts may have been a correctly * functioning device sharing an IRQ with the failing one)
So sounds hardware related. Whether it's the board itself or an add-in card I'm not sure. If possible remove all add-in cards that you can to see if the issue goes away. Also disable all devices in the BIOS that your not using (secondary IDE ports, serial ports, parallel ports etc), just to rule those out.
Of the roughly 1200 systems I've run with linux over the years I never recall encountering this message.
nate