From: Khalid Aziz <khalid@fc.hp.com>
To: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>
Cc: Doug Ledford <dledford@redhat.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: scsi_scan problem.
Date: Fri, 16 Mar 2001 16:40:29 -0700 [thread overview]
Message-ID: <3AB2A46D.B10CF743@fc.hp.com> (raw)
In-Reply-To: <3AB028BE.E8940EE6@redhat.com> <3AB29636.64C90827@neuronet.pitt.edu>
"Rafael E. Herrera" wrote:
>
> sr0: scsi3-mmc drive: 16x/16x xa/form2 changer
> sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
> sr1: scsi3-mmc drive: 16x/16x xa/form2 changer
> sr1: CDROM (ioctl) reports ILLEGAL REQUEST.
> sr2: scsi3-mmc drive: 16x/16x xa/form2 changer
> sr2: CDROM (ioctl) reports ILLEGAL REQUEST.
> sr3: scsi3-mmc drive: 16x/16x xa/form2 changer
> sr3: CDROM (ioctl) reports ILLEGAL REQUEST.
> sr4: scsi3-mmc drive: 16x/16x xa/form2 changer
> sr4: CDROM (ioctl) reports ILLEGAL REQUEST.
> sr5: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
> SCSI device sda: 17783240 512-byte hdwr sectors (9105 MB)
> sda: sda1 sda2 sda3 sda4
> SCSI device sdb: 8388315 512-byte hdwr sectors (4295 MB)
> sdb: sdb1
My guess is, ILLEGAL REQUEST is caused by the sr driver issuing
"Mechanism Status" (0xbd) command to the CDROM drives sr0, sr1, sr2, sr3
and sr4. The reason sr driver is issuing this command is because the
loading mechanism type field in CD-ROM capabilities page is set to 0x4
(changer). Does the Nakamichi drive put the changer mechanism on a
separate LUN, e.g. 1? If so, maybe the "Mechanism Status" commnad should
go to LUN 1 but cdrom_read_mech_status() does not set the LUN field in
cgc.cmd[1] to any value other than 0. Could this be the reason for
ILLEGAL REQUEST?
--
Khalid
====================================================================
Khalid Aziz Linux Development Laboratory
(970)898-9214 Hewlett-Packard
khalid@fc.hp.com Fort Collins, CO
next prev parent reply other threads:[~2001-03-16 23:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 2:28 scsi_scan problem Doug Ledford
2001-03-15 2:35 ` Pete Zaitcev
2001-03-15 3:03 ` Doug Ledford
2001-03-15 3:09 ` Doug Ledford
2001-03-16 16:53 ` Ishikawa
2001-03-16 19:33 ` Doug Ledford
2001-03-16 20:10 ` Peter Rival
2001-03-17 2:08 ` Ishikawa
2001-03-15 5:06 ` Bob Frey
2001-03-15 5:19 ` Doug Ledford
2001-03-16 22:39 ` Rafael E. Herrera
2001-03-16 22:54 ` Doug Ledford
2001-03-16 23:40 ` Khalid Aziz [this message]
2001-03-17 0:12 ` Patrick Mansfield
2001-03-17 1:56 ` Doug Ledford
2001-03-17 3:37 ` Rafael E. Herrera
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=3AB2A46D.B10CF743@fc.hp.com \
--to=khalid@fc.hp.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=raffo@neuronet.pitt.edu \
/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