Re: ATA errors corrupt other I/O & set / readonly

[Robert Hancock <hancockrwd@xxxxxxxxx>]

On 05/02/2012 02:59 AM, Felix Miata wrote:
> Two weeks ago on recommendation of downstream bug owner I filed
> https://bugzilla.kernel.org/show_bug.cgi?id=43128 expecting to see some
> kind of non-delayed reaction from someone either in the bug or here, and
> am quite disappointed that nothing has yet happened. Is the bug's owner
> sick, on holiday, or at a convention?
>
> I originally resisted filing because I believe that actual problem is
> the device's and not kernel or drivers. Yet, that it is possible for any
> such device failure to cause system corruption doesn't seem right
> either. So, can someone please comment on the likelihood that this bug
> can or will be fixed? I would like someone to respond here or in the bug
> before proceeding to try again to convince the manufacturer its product
> is defective and get a refund instead of yet another replacement of a
> defective product with another defective product.
>
> Once I return it for refund I will no longer be able to follow up on the
> bugs I filed, yet I need a working device that doesn't require I figure
> out a correct cmdline workaround for every one of the several systems it
> ever needs to be connected to.
>
> Please, what should I do?

It's hard to follow the discussion in the openSUSE bug report. I'm not 
sure if there was any dmesg posted from the case where other IO was 
being interfered with by the problems with the external device. In AHCI 
mode that really shouldn't happen, but in IDE mode on Intel controllers 
it may be more possible because of the PATA emulation that's effectively 
being done by the controller.

It's not possible to put in a blacklist entry for a specific SATA 
enclosure because they're essentially a passive device and there's no 
way to identify them through software (unless they have a custom ID 
string like the WD MyBook drives). If it only works properly at 1.5 Gbps 
then a module/boot parameter may be the best solution.
--
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