public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Florin Iucha <florin@iucha.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: spurious completions during NCQ?
Date: Wed, 06 Jun 2007 08:28:07 -0600	[thread overview]
Message-ID: <4666C477.1070603@shaw.ca> (raw)
In-Reply-To: <fa.Nigm+GFAuAW+QzfgqTUfmHJoFfU@ifi.uio.no>

Florin Iucha wrote:
> Hello,
> 
> I was working on a I/O heavy workload (parsing 100K spam messages to
> extract certain structures) when I got this in the kernel log:

..

> 
> 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?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-06-06 14:28 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 ` Robert Hancock [this message]
2007-06-07 12:04   ` spurious completions during NCQ? Florin Iucha
2007-06-08 12:55     ` Tejun Heo
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=4666C477.1070603@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=florin@iucha.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox