mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	LKML-SCSI <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	mike.miller@hp.com
Subject: Re: READ CAPACITY (16) failing
Date: Tue, 14 Apr 2009 13:23:37 -0500	[thread overview]
Message-ID: <20090414182337.GA5999@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <1239402518.3393.9.camel@mulgrave>

On Fri, Apr 10, 2009 at 03:28:38PM -0700, James Bottomley wrote:
> > 
> > Why would I never the see the command in the driver?
> 
> Because your devices are reporting compliance to a standard before RC16
> was implemented (we have a check in sd_try_rc16_first() to see if you
> comply to higher than SBC-2).  Then, after you've failed this, if you
> don't return the conventional 0xffffffff to RC10, we never retry with
> RC16.

Thanks, James, that looks like the culprit. The LUN actually reports that it
is a SCSI_SPC_3 device but the controller reports SCSI_UNKNOWN. I'll work
with the firmware guys to fix that.
Oddly enough, others here don't report seeing the same RC16 failure. Gets
better and better.

Thanks,
mikem

      reply	other threads:[~2009-04-14 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 19:43 Mike Miller (OS Dev)
2009-04-08 19:54 ` Matthew Wilcox
2009-04-09 15:22   ` Mike Miller (OS Dev)
2009-04-10 19:31   ` Mike Miller (OS Dev)
2009-04-10 21:04     ` Douglas Gilbert
2009-04-10 22:28     ` James Bottomley
2009-04-14 18:23       ` Mike Miller (OS Dev) [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=20090414182337.GA5999@beardog.cca.cpqcorp.net \
    --to=mikem@beardog.cca.cpqcorp.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mike.miller@hp.com \
    /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
all inboxes | Powered by JetHome®