kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
To: Kernel Testers List
	<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Paolo Ornati <ornati-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>,
	Tejun Heo <htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Subject: [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS
Date: Sun, 01 Mar 2009 17:28:06 +0100	[thread overview]
Message-ID: <49AAB796.1010709@fisher-privat.net> (raw)

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.

Alexey

             reply	other threads:[~2009-03-01 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 16:28 Alexey Fisher [this message]
     [not found] ` <49AAB796.1010709-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-03-02  7:20   ` [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS Tejun Heo
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=49AAB796.1010709@fisher-privat.net \
    --to=bug-track-m18mab7tlt0ycq4ww13eyl6hyfs7nttn@public.gmane.org \
    --cc=htejun-Re5JQEeQqe8AvxtiuMwx3w@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).