From: Robert Hancock <hancockrwd@gmail.com>
To: Felix Miata <mrmazda@earthlink.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: ATA errors corrupt other I/O & set / readonly
Date: Sat, 19 May 2012 17:28:26 -0600 [thread overview]
Message-ID: <4FB82C9A.9020508@gmail.com> (raw)
In-Reply-To: <4FA0F76E.3050509@earthlink.net>
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.
next prev parent reply other threads:[~2012-05-19 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 8:59 ATA errors corrupt other I/O & set / readonly Felix Miata
2012-05-19 23:28 ` Robert Hancock [this message]
2012-05-20 4:56 ` Felix Miata
2012-05-25 1:03 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB82C9A.9020508@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mrmazda@earthlink.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).