All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Linux SCSI <linux-scsi@vger.kernel.org>
Subject: Re: SAI_READ_CAPACITY_16?
Date: Wed, 06 Apr 2005 14:27:14 -0400	[thread overview]
Message-ID: <1112812035.5555.20.camel@mulgrave> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458BFF2211@otce2k01.adaptec.com>

On Wed, 2005-04-06 at 12:00 -0400, Salyzyn, Mark wrote:
> For some reason, sd_read_capacity (in sd.c) in the 2.6.9-5.EL (RHEL4)
> kernel is not issuing the SERVICE_REQUEST_IN+SAI_READ_CAPACITY_16
> command to the queuecommand handler (the handler is not even called),
> even though it instruments up that the command is issued (and returns
> not supported). The READ_CAPACITY call makes it through successfully
> indicating 0xFFFFFFFF capacity to trigger the SAI_READ_CAPACITY_16
> request fine. Could there be a bug in the scsi layers reissuing commands
> reusing the request structure misdirecting the requests?

The person who coded it gave a success report on it ... and I've had
several others since then.

On a 32 bit system, you have to have CONFIG_LBD for it to work.

This code is pretty verbose, what are your kernel traces?

James



  parent reply	other threads:[~2005-04-06 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 16:00 SAI_READ_CAPACITY_16? Salyzyn, Mark
2005-04-06 16:11 ` SAI_READ_CAPACITY_16? Ming Zhang
2005-04-06 18:27 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-06 18:30 SAI_READ_CAPACITY_16? Salyzyn, Mark
2005-04-06 18:32 ` SAI_READ_CAPACITY_16? Ming Zhang

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=1112812035.5555.20.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.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 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.