From: florin@iucha.net (Florin Iucha)
To: Tejun Heo <htejun@gmail.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: spurious completions during NCQ?
Date: Fri, 8 Jun 2007 08:11:57 -0500 [thread overview]
Message-ID: <20070608131157.GH30661@iucha.net> (raw)
In-Reply-To: <466951DE.9070004@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3317 bytes --]
On Fri, Jun 08, 2007 at 09:55:58PM +0900, Tejun Heo wrote:
> Florin Iucha wrote:
> >> It means the drive reported command tags were completed that were not
> >> outstanding. What kind of drive is this?
> >
> > [ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156
> > 301488
> > [ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max UDMA/100
> > [ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32)
> > [ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156
> > 301488
>
> Please report the result of 'hdparm -I /dev/sda'. We'll probably have
> to blacklist it for NCQ.
Here it is: I only jumbled the serial number a bit.
/dev/sda:
ATA device, with non-removable media
Model Number: HITACHI HTS541680J9SA00
Serial Number: SB******I57L4A
Firmware Revision: SB2IC7EP
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128 (0x80)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
SET_MAX security extension
Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
* SATA-I signaling speed (1.5Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
Non-Zero buffer offsets in DMA Setup FIS
DMA Setup Auto-Activate optimization
Device-initiated interface power management
In-order data delivery
* Software settings preservation
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
42min for SECURITY ERASE UNIT.
Checksum: correct
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-08 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Nigm+GFAuAW+QzfgqTUfmHJoFfU@ifi.uio.no>
2007-06-06 14:28 ` spurious completions during NCQ? Robert Hancock
2007-06-07 12:04 ` Florin Iucha
2007-06-08 12:55 ` Tejun Heo
2007-06-08 13:11 ` Florin Iucha [this message]
2007-06-08 13:20 ` [PATCH] libata: disable NCQ for HITACHI HTS541680J9SA00/SB21C7EP Tejun Heo
2007-06-08 15:28 ` Alan Cox
2007-06-10 2:41 ` Jeff Garzik
2007-06-08 15:28 ` spurious completions during NCQ? Alan Cox
2007-06-15 7:51 ` Massimiliano Hofer
2007-06-18 5:30 ` Tejun Heo
2007-06-06 5:28 Florin Iucha
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=20070608131157.GH30661@iucha.net \
--to=florin@iucha.net \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=linux-kernel@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.