Hello,
On Fri, Feb 18, 2011 at 10:20:43AM +1100, Steven Haigh wrote:
> With this patch applied, my rebuilt kernel based on 2.6.32.26 (due
> to Xen Dom0 requirements) gives the following:
>
> ata9: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
> ata9: SError: { PHYRdyChg CommWake }
> ata9: hard resetting link
> ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata9.00: failed to IDENTIFY (I/O error, err_mask=0x202)
> ata9: hard resetting link
> ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata9.00: failed to IDENTIFY (I/O error, err_mask=0x202)
> ata9: hard resetting link
> ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata9.00: failed to IDENTIFY (I/O error, err_mask=0x202)
> ata9: hard resetting link
> ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata9: EH complete
So, retrying doesn't help at all.
> I would really like to eliminate the possibility of it being my
> esata enclosure or the sata -> esata cable by using another cable
> and/or array for testing. New cables will be a few days off as I
> don't have any of these cables hanging around. My gut feeling says
> its the cable - as the enclosure works fine via the USB port -
> however that isn't conlusive proof that the esata port is working as
> it should!
Yeah, it looks like something is wrong with the setup. Please let us
know how the testing goes with the new cable (hopefully shorter).
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
