All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: "Lanstein, Alex C" <aclan@conncoll.edu>, linux-ide@vger.kernel.org
Subject: Re: NCQ change  on 2007-12-07
Date: Thu, 13 Mar 2008 12:28:10 +0900	[thread overview]
Message-ID: <47D89F4A.7090008@gmail.com> (raw)
In-Reply-To: <47D89A58.6010301@shaw.ca>

Hello,

Robert Hancock wrote:
> I don't think the driver is to blame for this one. CPB resp_flags of 2
> indicates the controller says that tag is "released", i.e. drive has
> been given the command but not completed. If it's timing out in that
> state, either the NCQ implementation is bad enough that it allows
> certain queued commands to starve for over 30 seconds, or the drive is
> just forgetting about them entirely.
> 
> Unfortunately, if the firmware revision does indeed appear the same on
> both sets of drives, the only automated way we could likely address the
> problem would be to blacklist NCQ on all of those drives of that
> model/revision..

Hmm... it's weird that this problem hasn't been reported on other
controllers.  Lanstein, can you be persuaded into trying out another NCQ
capable controller?

-- 
tejun

      reply	other threads:[~2008-03-13  3:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D8AE5DC69BFCA64989BE8E46BCF0047303B24F2E@MAPLE.conncoll.edu>
     [not found] ` <47D76B7D.8010808@gmail.com>
2008-03-12 15:08   ` NCQ change on 2007-12-07 Lanstein, Alex C
2008-03-13  3:07     ` Robert Hancock
2008-03-13  3:28       ` Tejun Heo [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=47D89F4A.7090008@gmail.com \
    --to=htejun@gmail.com \
    --cc=aclan@conncoll.edu \
    --cc=hancockr@shaw.ca \
    --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.