From: Tejun Heo <htejun@gmail.com>
To: Florin Iucha <florin@iucha.net>
Cc: Robert Hancock <hancockr@shaw.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: spurious completions during NCQ?
Date: Fri, 08 Jun 2007 21:55:58 +0900 [thread overview]
Message-ID: <466951DE.9070004@gmail.com> (raw)
In-Reply-To: <20070607120430.GB30661@iucha.net>
Florin Iucha wrote:
> On Wed, Jun 06, 2007 at 08:28:07AM -0600, Robert Hancock wrote:
>>> This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel
>>> 2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel
>>> Wi-Fi - but that should not count).
>>>
>>> The laptop came with Windows but I blew that away - did I mess some
>>> thing up regarding HPA and its ilk?
>> 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.
--
tejun
next prev parent reply other threads:[~2007-06-08 12:56 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 [this message]
2007-06-08 13:11 ` Florin Iucha
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=466951DE.9070004@gmail.com \
--to=htejun@gmail.com \
--cc=florin@iucha.net \
--cc=hancockr@shaw.ca \
--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.