> Anyway, to cut a long story short, when a command goes wrong, the get > sense packet command does not seem to generate an end of event > interrupt and as a result the command times out (after 60 seconds in > my driver) but the correct sense key is then returned on a read of the > Data register. Could be the case for a weird device. > My question is whether this (ie sense times out but still returns the > right result) is this behaviour you would expect in a "normal" ATAPI > device? No. I would take it as indication of an IRQ delivery problem, or given the device you have perhaps an expectation that request sense must be issued as a polling command with nIEN. - 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