From: Tejun Heo <tj@kernel.org>
To: giulioo@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: Re: Please add ST3120827AS 3.42 to NCQ blacklist
Date: Thu, 12 Feb 2009 10:47:33 +0900 [thread overview]
Message-ID: <49937FB5.3000608@kernel.org> (raw)
In-Reply-To: <20090202132824.09984F805@i3.golden.dom>
Hello,
Giulio Orsero wrote:
> Supermicro P8SC8, CENTOS/RHEL 5.x 2.6.18-128.el5
> HD: Seagate SATA ST3120827AS fw3.42 [2 disks in md raid1]
>
> 00:1f.1 0101: 8086:266f (rev 03)
> 00:1f.2 0101: 8086:2652 (rev 03)
>
> 2652 is handled by both ata_piix and ahci.
> Using ata_piix everything is fine, using ahci will cause periodic errors
> like:
>
> ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
> ata1.00: cmd 61/08:00:4d:6d:c0/00:00:00:00:00/40 tag 0 ncq 4096 out
> res 40/00:00:b5:95:a7/00:00:00:00:00/40 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }
> ata1: hard resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
>
> Using
> echo 1 > /sys/block/sda/device/queue_depth
> echo 1 > /sys/block/sdb/device/queue_depth
> will eliminate the issue, so please add
> { "ST3120827AS", "3.42", ATA_HORKAGE_NONCQ },
> to the NCQ blacklist.
That's a 7200.7 which has been quite popular && happens to be used
extensively during libata development, so I'm highly doubtful the
problem is a wide spread one. The problem is more likely to be
something specific to your configuration.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-02-12 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 13:28 Please add ST3120827AS 3.42 to NCQ blacklist Giulio Orsero
2009-02-12 1:47 ` Tejun Heo [this message]
2009-02-12 4:30 ` 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=49937FB5.3000608@kernel.org \
--to=tj@kernel.org \
--cc=giulioo@pobox.com \
--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 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).