On Thu, Jan 12, 2012 at 5:37 PM, Jack Wang <jack_wang@xxxxxxxxx> wrote: >> For example libata will reset 3 times with increasing wait times (10s, >> 10s, 35s). On the last attempt it will slow down the phy to give the >> ata device a better chance of connecting. libsas is just doing 3 >> 500ms tries at full speed and then giving up. > [Jack Wang] > Yes， in our internal test I expand the time to 10s, but I'm not sure this will be accepted by mainline kernel. Do you happen to have logs of a passing and failing case, i.e. before and after adding the 10s time delay change? I think having libata do it's normal link recovery in this case would solve both problems of giving enough time for ata device to come up, and allowing the initial scan to find the device and let the initial trip through ata eh manage link. But it would be a pretty big change from what libsas is doing currently for sata discovery. -- 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
