----- Original Message ----- > Did you try any workaround boot options such as irqpoll, pci=nocrs or >whatever?
Actually, it turns out that booting with "irqpoll=1" simply means that this problem takes longer to happen: irq 17: nobody cared (try booting with the "irqpoll" option) Pid: 3347, comm: wineserver Not tainted 3.5.3 #2 Call Trace: [<c1063806>] ? __report_bad_irq+0x11/0x94 [<c1063a2d>] ? note_interrupt+0x120/0x19b [<c1062325>] ? handle_irq_event_percpu+0xe8/0xfb [<c1062361>] ? handle_irq_event+0x29/0x40 [<c1064163>] ? handle_fasteoi_irq+0x67/0x90 [<c1003957>] ? handle_irq+0x63/0x70 [<c1003625>] ? do_IRQ+0x2e/0x83 [<c1229829>] ? common_interrupt+0x29/0x30 handlers: [<f8d09b75>] azx_interrupt [snd_hda_intel] Disabling IRQ #17 Cheers, Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
