On Thu, Jul 14, 2011 at 05:37:37PM +0000, Derry Bryson wrote:
> Hi:
>
> Dmesg with second timing value set to 1000 always, hotplugging WD 3TB drive:
>
> [ 139.145917] ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xf
> [ 139.156180] ata5.00: SError: { PHYRdyChg CommWake DevExch }
> [ 139.166619] ata5.00: hard resetting link
> [ 140.430401] ata5.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
> [ 140.430453] ata5.00: issuing IDENTIFY
> [ 140.430480] ata5.00: IDENTIFY failed, irq_stat=0x60002 cerr=4
> [ 140.430521] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x11)
...
> [ 145.431276] ata5.00: hard resetting link
> [ 145.431298] ata5.00: XXXX hardreset hotplugged = false
> [ 145.431304] ata5.00: XXX0 hardreset debounce 5 100 2000
> [ 145.431310] ata5.00: XXX1 hardreset debounce 5 1000 2000
> [ 146.690413] ata5.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
...
> [ 152.940451] ata5.00: issuing IDENTIFY
> [ 152.940477] ata5.00: IDENTIFY failed, irq_stat=0x60002 cerr=4
> [ 152.940518] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x11)
So, no change. Weird. I think we need to implement retry backoff
properly anyways but am still wondering why probing failure behaves
differently for you. I'll try with similar drive but maybe it's
difference in PMP firmware?
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
