Hello.
Steven Scholz wrote:
Looks like a spurious interrupt... Is your IDE IRQ shared with other
devices?
..
But IIUC then first the HDD times out, the ide driver handles this and
then an irq occurs which is probably the irq the driver was waiting for.
The driver is *not* waiting for any IRQ after issuing MULTWRITE_EXT,
that's why it's "unexpected".
Hmm. But how does he "know" when that MULTWRITE_EXT is finished!?
It's considered finished in this case as there was no starting DRQ
"handshake". The first interrupt should happen only after the first block of
data is written.
Steven
MBR, Sergei
-
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
