From: Frans Pop <elendil@planet.nl>
To: linux-ide@vger.kernel.org
Cc: Tejun Heo <htejun@gmail.com>
Subject: Re: ata1.00: spurious completions during NCQ
Date: Thu, 4 Oct 2007 10:18:37 +0200 [thread overview]
Message-ID: <200710041018.38140.elendil@planet.nl> (raw)
In-Reply-To: <47044D36.4090708@gmail.com>
On Thursday 04 October 2007, Tejun Heo wrote:
> Frans Pop wrote:
> > On 15 August 2007 Tejun Heo wrote:
> >> You don't need to worry too much as long as errors are properly,
> >> recovered. All commands are retried and you won't lose any data.
> >> Please report if the spurious NCQ problem happens again. Thanks.
> >
> > I've just received a logcheck mail with another one. I have not seen
> > any in the time between my initial mail [1] and now, so this is the
> > second occurrence in 1.5 months. The message is slightly different this
> > time.
> >
> > I'm currently running 2.6.23-rc8 + CFS patchset.
>
> Please post the result of "hdparm -I /dev/sda". Thanks.
/dev/sda:
ATA device, with non-removable media
Model Number: HDT722516DLA380
Serial Number: VDKE1BTCDZ1KHR
Firmware Revision: V43OA96A
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: 268435455
LBA48 user addressable sectors: 321672960
device size with M = 1024*1024: 157066 MBytes
device size with M = 1000*1000: 164696 MBytes (164 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns 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
* DOWNLOAD_MICROCODE
Advanced Power Management feature set
Power-Up In Standby feature set
SET_FEATURES required to spinup after power up
Address Offset Reserved Area Boot
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
Media Card Pass-Through
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* URG for READ_STREAM[_DMA]_EXT
* URG for WRITE_STREAM[_DMA]_EXT
* SATA-I signaling speed (1.5Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
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
78min for SECURITY ERASE UNIT.
Checksum: correct
prev parent reply other threads:[~2007-10-04 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 12:43 ata1.00: spurious completions during NCQ Frans Pop
2007-10-04 2:17 ` Tejun Heo
2007-10-04 8:18 ` Frans Pop [this message]
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=200710041018.38140.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=htejun@gmail.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 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.