From: "Eric D. Mudama" <edmudama@gmail.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: "Jens Axboe" <axboe@suse.de>, "Tejun Heo" <htejun@gmail.com>,
"Nicolas Mailhot" <nicolas.mailhot@gmail.com>,
"Mark Lord" <liml@rtr.ca>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
"Carlos Pardo" <Carlos.Pardo@siliconimage.com>
Subject: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
Date: Wed, 1 Mar 2006 19:20:22 -0700 [thread overview]
Message-ID: <311601c90603011820u4fc89b04te1be39b9ed2ef35b@mail.gmail.com> (raw)
In-Reply-To: <4406512A.9080708@pobox.com>
On 3/1/06, Jeff Garzik <jgarzik@pobox.com> wrote:
> This also begs the question... what controller was being used, when the
> single Maxtor device listed in the blacklist was added? Perhaps it was
> a problem with the controller, not the device.
>
> Jeff
As reported here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177951
the controller was a 3114, and the bug was "fixed" by blacklisting his
Maxtor drive's FUA support. I'd like Maxtor drives to be
un-blacklisted if possible.
--eric
next prev parent reply other threads:[~2006-03-02 2:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 19:00 LibPATA code issues / 2.6.15.4 Nicolas Mailhot
2006-03-01 19:22 ` Mark Lord
2006-03-01 23:12 ` Nicolas Mailhot
2006-03-01 23:31 ` Jeff Garzik
2006-03-02 1:19 ` Eric D. Mudama
2006-03-02 1:39 ` Eric D. Mudama
2006-03-02 1:56 ` FUA and 311x (was Re: LibPATA code issues / 2.6.15.4) Jeff Garzik
2006-03-02 1:58 ` Jeff Garzik
2006-03-02 2:20 ` Eric D. Mudama [this message]
2006-03-02 2:46 ` Jeff Garzik
2006-03-02 3:00 ` Eric D. Mudama
2006-03-02 3:06 ` Jeff Garzik
2006-03-02 3:13 ` Tejun Heo
2006-03-02 3:16 ` Mark Lord
2006-03-02 3:18 ` Jeff Garzik
2006-03-02 6:23 ` Eric D. Mudama
2006-03-02 9:00 ` Sander
2006-03-02 11:52 ` Jeff Garzik
2006-03-02 8:57 ` Sander
2006-03-03 0:34 ` Mark Lord
2006-03-02 16:12 ` Nicolas Mailhot
2006-03-02 16:07 ` Nicolas Mailhot
2006-03-02 16:03 ` Nicolas Mailhot
2006-03-02 16:05 ` Nicolas Mailhot
2006-03-02 7:22 ` Jens Axboe
2006-03-02 15:59 ` Nicolas Mailhot
2006-03-02 16:37 ` Jeff Garzik
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=311601c90603011820u4fc89b04te1be39b9ed2ef35b@mail.gmail.com \
--to=edmudama@gmail.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=axboe@suse.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.mailhot@gmail.com \
/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
all inboxes | Powered by JetHome®