public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Liong Hoong <liongshliongsh@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: sg_io_hrd_t - host_status error (0x05)
Date: Sat, 01 May 2004 11:53:56 +1000	[thread overview]
Message-ID: <40930334.4040908@torque.net> (raw)
In-Reply-To: <20040430071234.67120.qmail@web40005.mail.yahoo.com>

Liong Hoong wrote:
> Hi,
> 
> Sorry if there is any misunderstanding in my previous
> questions.
> I would like to ask, 
> I am using Linux Red Hat 8.0, kernel 2.4.18. I used
> the SG driver version 3 without any modification of
> the kernel. I encountered host_status error (0x05)
> ONLY on sending opcodes from 0x80 to 0x9f. Can anyone
> give me hints on why or which part of the kernel codes
> that might failed this specific range of opcodes? Or
> is there any work around or patches? Anyone out there
> did experience similar problems and like to share with
> me?

Sean,
I assume that you have already determined (via another OS)
that the device really does accept 16 byte SCSI commands
in that opcode range.

As mentioned in my previous post the 12 to 16 byte cdb
expansion occurred in lk 2.4.15. Maybe the usb-storage driver
took a few versions to catch up. Apart from vendor specific
commands, there would not be a lot of demand for the
usb-storage driver to support 16 byte commands.
Perhaps you should try a more recent version of the linux
kernel. If the problem persists then you are more likely to
get help.

Doug Gilbert



  reply	other threads:[~2004-05-02  4:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  3:11 sg_io_hrd_t - host_status error (0x05) Liong Hoong
2004-04-24  3:47 ` Douglas Gilbert
2004-04-27  3:43   ` Liong Hoong
2004-04-30  7:12     ` Liong Hoong
2004-05-01  1:53       ` Douglas Gilbert [this message]
2004-05-07  4:25         ` Liong Hoong

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=40930334.4040908@torque.net \
    --to=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=liongshliongsh@yahoo.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