From: Tejun Heo <htejun@gmail.com>
To: diego torres <dtorres@coral.dnsalias.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: blacklisting ST3500630AS as not able to do NCQ
Date: Mon, 29 Oct 2007 15:14:34 +0900 [thread overview]
Message-ID: <47257A4A.1000806@gmail.com> (raw)
In-Reply-To: <1993911428.20071007225627@coral.dnsalias.org>
diego torres wrote:
> Hi there,
>
> This seagate drive ST3500630AS is being recognized as NCQ capable by
> hdparm, and has the default queue_depth of 31, so i think it should
> work ok. But there are some problems when using smartmontools (for
> example in short test mode) as seen in dmesg:
>
> ata2.00: exception Emask 0x2 SAct 0x9 SErr 0x0 action 0x2 frozen
> ata2.00: (spurious completions during NCQ issue=0x0 SAct=0x9 FIS=004040a1:00000004)
> ata2.00: cmd 61/08:00:f4:28:4e/00:00:00:00:00/40 tag 0 cdb 0x0 data 4096 out
> res 40/00:00:f4:28:4e/00:00:00:00:00/40 Emask 0x2 (HSM violation)
> ata2.00: cmd 61/08:18:dc:c8:d7/00:00:00:00:00/40 tag 3 cdb 0x0 data 4096 out
> res 40/00:00:f4:28:4e/00:00:00:00:00/40 Emask 0x2 (HSM violation)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
> sd 1:0:0:0: [sdb] Write Protect is off
> sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> All this problems dissapear when setting queue_depth to 1.
>
> After cheking the seagate website, there is no mention to NCQ in the
> spec sheet of this drive, although there are models tagged as using
> NCQ interface, for example ST3500620AS
How reproducible is the problem?
--
tejun
next prev parent reply other threads:[~2007-10-29 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 20:56 blacklisting ST3500630AS as not able to do NCQ diego torres
2007-10-29 6:14 ` Tejun Heo [this message]
2007-10-30 0:06 ` Re[2]: " diego torres
2007-10-30 10:59 ` Michael Tokarev
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=47257A4A.1000806@gmail.com \
--to=htejun@gmail.com \
--cc=dtorres@coral.dnsalias.org \
--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.