Elias Oltmanns wrote: >> - tf.flags |= ATA_TFLAG_DEVICE | ATA_TFLAG_ISADDR; >> + tf.flags |= ATA_TFLAG_DEVICE | ATA_TFLAG_ISADDR | ATA_TFLAG_DEVICE; > > After my embarrassing failure to parse a macro correctly a few days > back, I've got to be careful ;-). But still, what good does that patch > do? It doesn't really change anything, does it? Hehheh, I suppose it's my turn for embarrassment. > As a wild guess, I'm wondering whether ata_eh_revalidate_and_attach() > has anything to do with it. Unless you have a better suggestion, perhaps > the following debug patch would give some useful information. I don't have much idea at this point. To the drive, it shouldn't look any different. Ah... it's ata_piix, right? ata_piix doesn't have PHY event IRQ, so it could be that the command issued by hdparm did trigger PHY event but didn't get noticed by EH while the condition triggered by IDLE IMMEDIATE did. One way to find out would be adding SCR print outs on command completion. 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
