kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alexey Fisher
	<bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
Cc: Kernel Testers List
	<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Paolo Ornati <ornati-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>,
	Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Subject: Re: [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS
Date: Mon, 02 Mar 2009 16:20:50 +0900	[thread overview]
Message-ID: <49AB88D2.3020701@gmail.com> (raw)
In-Reply-To: <49AAB796.1010709-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>

Hello,

Alexey Fisher wrote:
> Commit da6f0ec2d54acf545e784363aa5bad0dafc5ffa8
> libata: blacklist NCQ on Seagate Barracuda ST380817AS
> 
> I tested Seagate Barracuda ST380817AS on my system without the blacklist
>  entry on system with ext4 fs and it seems to work. Two days with normal
> load, tar, kvm, torrent... i can't reproduce the error described in this
> commit.
> 
> I use board with ICH10R south bridge, AHCI mode.

Heh.. I don't know.  Things like this are pretty difficult to reliably
reproduce and verify.  As a rule of thumb, cases which are reported
multiple times and in close proximity with existing entries in product
line or firmware revision tend to be included.  Given that earlier NCQ
implementations didn't actually help performance much (or rather often
degraded it) and it has a sibling entry with the same firmware
revision, I'm a bit reluctant to lift the blacklist.  You can
overrided it with kernel parameter "libata.force=P.DD:ncq" where P is
the ata port number and DD is the device number.

Thanks.

-- 
tejun

  parent reply	other threads:[~2009-03-02  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 16:28 [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS Alexey Fisher
     [not found] ` <49AAB796.1010709-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-03-02  7:20   ` Tejun Heo [this message]
2009-03-03 19:50   ` Paolo Ornati
     [not found]     ` <20090303205034.6fa9a5d5-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>
2009-03-03 20:39       ` Alexey Fisher
     [not found]         ` <49AD9584.6070603-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-03-04 19:31           ` Paolo Ornati

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=49AB88D2.3020701@gmail.com \
    --to=htejun-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org \
    --cc=jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ornati-dbx96nzIXN7OeuqD6ShaSA@public.gmane.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 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).