I'm extracting this from a different thread hoping for more help :) Thanks Rudolf for all the help so far.
This is the last "funny" snippet from a Linux boot log with ACPI enabled: irq 9: nobody cared (try booting with the "irqpoll" option) Pid: 0, comm: swapper Not tainted 2.6.27-11-generic #1 Call Trace: <IRQ> [<ffffffff8029e8ab>] __report_bad_irq+0x2b/0x90 [<ffffffff8029ea47>] note_interrupt+0x137/0x170 [<ffffffff8029f1dd>] handle_fasteoi_irq+0xed/0x110 [<ffffffff80215b16>] do_IRQ+0x86/0x100 [<ffffffff80212f0e>] ret_from_intr+0x0/0x29 <EOI> [<ffffffff8022d236>] ? native_safe_halt+0x6/0x10 [<ffffffff805068ca>] ? atomic_notifier_call_chain+0x1a/0x20 [<ffffffff8021ac35>] ? default_idle+0x55/0x60 [<ffffffff80210e95>] ? cpu_idle+0x75/0x110 [<ffffffff804fe845>] ? start_secondary+0x97/0xc2 handlers: [<ffffffff803d2b90>] (acpi_irq+0x0/0x2b) Disabling IRQ #9 Freeing initrd memory: 8460k freed audit: initializing netlink socket (disabled) This IRQ is very active > > 9: 1 276 15 99709 IO-APIC-fasteoi acpi > > Huh quite big number. Is it from coreboot or legacy BIOS? It's from Coreboot. Here's the same line from the factory BIOS: 9: 0 0 0 0 IO-APIC-fasteoi acpi > Maybe some ACPI GP > timer is generating the IRQ9? How do you find an interrupt source that's going crazy like that? When I boot with acpi=off I IRQ9 doesn't even get registered. Thanks, Myles -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
