Hello, On 01/11/2010 02:12 PM, Benjamin Herrenschmidt wrote: > Tejun, what's your take here ? It looks like reading the status reg > is not enough to bring the interrupt down. We could try to disable_irq > in freeze() (we know we don't share interrupts in the case of macio) > and re-enable it right after firing off the first taskfile maybe ? It would be best if the controller has an IRQ pending bit and IRQ can be cleared as spurious on those bogus interrupts. The reason why SFF IDE interface is so prone to IRQ storm is because there's no way the driver can tell whether the controller is raising interrupt or not. Does the controller have a way to clear IRQ other than reading the status reg? Thanks. -- 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
