From: Felix Miata <mrmazda@earthlink.net>
To: linux-ide@vger.kernel.org
Subject: ATA errors corrupt other I/O & set / readonly
Date: Wed, 02 May 2012 04:59:26 -0400 [thread overview]
Message-ID: <4FA0F76E.3050509@earthlink.net> (raw)
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?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
next reply other threads:[~2012-05-02 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 8:59 Felix Miata [this message]
2012-05-19 23:28 ` ATA errors corrupt other I/O & set / readonly Robert Hancock
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=4FA0F76E.3050509@earthlink.net \
--to=mrmazda@earthlink.net \
--cc=linux-ide@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.