From: Tejun Heo <htejun@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-ide@vger.kernel.org
Subject: Re: ata1.00: spurious completions during NCQ
Date: Thu, 04 Oct 2007 11:17:26 +0900 [thread overview]
Message-ID: <47044D36.4090708@gmail.com> (raw)
In-Reply-To: <200710011443.05629.elendil@planet.nl>
Frans Pop wrote:
> Hi,
>
> 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.
>
> kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x8 FIS=005040a1:00000004
> kernel: ata1.00: cmd 60/58:18:b3:56:bd/00:00:01:00:00/40 tag 3 cdb 0x0 data 45056 in
> kernel: res 50/00:58:b3:56:bd/00:00:01:00:00/40 Emask 0x2 (HSM violation)
> kernel: ata1: soft resetting port
> kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> kernel: ata1.00: configured for UDMA/133
> kernel: ata1: EH complete
> kernel: sd 0:0:0:0: [sda] 321672960 512-byte hardware sectors (164697 MB)
> kernel: sd 0:0:0:0: [sda] Write Protect is off
> kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Please post the result of "hdparm -I /dev/sda". Thanks.
--
tejun
next prev parent reply other threads:[~2007-10-04 2:17 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 [this message]
2007-10-04 8:18 ` Frans Pop
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=47044D36.4090708@gmail.com \
--to=htejun@gmail.com \
--cc=elendil@planet.nl \
--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.