Sorry to bring this up again, but I think that the current behavior of requiring a manual device reset, for some disks that are put to sleep with hdparm -Y is definitely wrong - I mailed Mark Lord, (the hdparm maintainer) who said:
> Yes, I agree: the IDE driver should automatically
> attempt a "device reset" at some point when trying
> to communicate with a drive that is not responding
> (eg. due to "hdparm -Y" or whatever).
Is this a known issue with some interface/drive combinations? I can only reproduce it with a Maxtor disk on a PIIX3 interface. After being put to sleep, the disk never responds until it is manually reset with hdparm -w.
I know you can achieve a similar effect by putting the disk in to standby, but putting it to sleep will reduce energy consumption, (by a tiny amount).
John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/