Geert, as hinted in my earlier patch series, this one bit me while debugging the SCSI/IDE deadlock on my Falcon. On Falcon, registering the IDE interrupt handler is taken care of by registering stdma_int() in the arch setup code, then passing the relevant IDE interrupt handler as argument to stdma_lock(). This ensures that the IDE inthandler is only called if IDE has acquired the ST-DMA lock, and avoids the IDE handler stepping on the SCSI handlers' toes if the ST-DMA is locked by SCSI. At some point in the past, the IDE interrupt was registered unconditionally even on m68k, resulting in both stdma_int() and ide_interrupt() being registered, again opening up the potential of IDE taking interrupts meant to be handled by SCSI (or floppy). This might result in deadlocking the SCSI driver if IDE releases the ST-DMA lock in error. The next patch changes the IDE core to only register the IDE handler if host->get_lock is not set - AFAIK m68k is the sole user of host->get_lock so we can rely on IDE interrupts being handled through the multiplexer whenever host->get_lock happens to be set. Cheers, Michael -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
