Thomas Gleixner wrote: > On Mon, 2007-03-12 at 17:31 +0100, Michal Piotrowski wrote: >> Calling initcall 0xc19154d8: piix_ide_init+0x0/0xbb() >> Calling initcall 0xc19155b6: generic_ide_init+0x0/0x16() >> Calling initcall 0xc191572e: ide_init+0x0/0x81() >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx >> ICH5: IDE controller at PCI slot 0000:00:1f.1 >> irq 5: nobody cared (try booting with the "irqpoll" option) >> [<c1604556>] show_trace_log_lvl+0x1a/0x2f >> [<c1604c2c>] show_trace+0x12/0x14 >> [<c1604cde>] dump_stack+0x16/0x18 >> [<c164341c>] __report_bad_irq+0x39/0x79 >> [<c16435eb>] note_interrupt+0x18f/0x1c8 >> [<c1643ec6>] handle_level_irq+0x95/0xcb >> [<c1605dd8>] do_IRQ+0xb4/0xe0 >> ======================= >> handlers: >> [<c174f55e>] (skge_intr+0x0/0x3ff) >> Disabling IRQ #5 > > I know this one :( > > It seems to be related to the BIOS spinning up the CDROM and leaving the > IDE controller in some weird state. When we come back the interrupt is > screaming and nobody cares, so it gets disabled. I have no clue yet, how > to handle this. > > Disabling the interrupt across suspend/resume helps, but does not work, > when the interrupt is shared with some other device. Similar thing can happen during initialization. I haven't actually instrumented the code but I think what happens is 1. the controller has IRQ stuck high (infrequent but possible) 2. the IRQ is already requested by another device 3. the IRQ gets disabled due to screaming interrupts at the moment ata_piix does pci_enable_device(). I think we can be much more resilient to screaming interrupts if we enable device with IRQ disabled and enable it after the device is initialized to some level, possibly when requesting IRQ. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
