From: Albert Lee <albertcc@tw.ibm.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: albertl@mail.com, YUP <yupadmin@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Tejun Heo <htejun@gmail.com>
Subject: Re: libata: CD and dvd devices not recognized
Date: Fri, 23 Mar 2007 11:21:01 +0800 [thread overview]
Message-ID: <4603479D.9070803@tw.ibm.com> (raw)
In-Reply-To: <4602979F.80002@ru.mvista.com>
Sergei Shtylyov wrote:
> Hello.
>
> Albert Lee wrote:
>
>> Thanks for the detailed log.
>> It looks like the bad INQUIRY command
>> "CDB (4:0,1,0) 12 01 00 00 fe 00 00 00 00" (INQUIRY, length=254,
>> EVPD=1)
>> is coming from the user space, not the SCSI mid-layer.
>
>
>> I guess two problems together caused this bug:
>> 1. Ubuntu Linux issues an incorrect INQUIRY command to the drive.
>> (Other distros seem to have the INQUIRY correct.)
>
>
> But what is incorrect about sending INQUIRY with EVPD bit?
Nothing wrong from the SCSI point of view.
However, in the early ATAPI spec (sff-8020i), this EVPD bit is
"reserved". And apprently some imperfect ATAPI CD-ROM drive doesn't
handle it well when EVPD = 1. :(
Hmm, how about the revised version:
1. Ubuntu Linux issues a correct INQUIRY command to the drive
which set EVPD = 1. However, EVPD is "reserved" per early ATAPI
spec and the AOpen 56X/AKH drive times out in this case.
...
--
albert
next prev parent reply other threads:[~2007-03-23 3:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 22:14 libata: CD and dvd devices not recognized YUP
2007-03-15 3:56 ` Albert Lee
2007-03-15 13:11 ` YUP
2007-03-15 17:32 ` Albert Lee
2007-03-16 10:16 ` YUP
2007-03-16 15:06 ` Albert Lee
2007-03-16 15:50 ` YUP
2007-03-17 13:29 ` Bartlomiej Zolnierkiewicz
2007-03-17 14:39 ` Albert Lee
2007-03-17 15:00 ` Bartlomiej Zolnierkiewicz
2007-03-17 18:38 ` YUP
2007-03-17 18:47 ` YUP
2007-03-17 19:12 ` Bartlomiej Zolnierkiewicz
2007-03-17 19:22 ` YUP
2007-03-17 20:07 ` Bartlomiej Zolnierkiewicz
2007-03-18 10:07 ` YUP
2007-03-18 15:10 ` Bartlomiej Zolnierkiewicz
2007-03-18 15:22 ` YUP
2007-03-18 15:54 ` Bartlomiej Zolnierkiewicz
2007-03-18 15:49 ` YUP
2007-03-18 22:48 ` YUP
2007-03-19 3:31 ` Albert Lee
2007-03-19 8:22 ` YUP
2007-03-19 8:29 ` Albert Lee
2007-03-19 12:10 ` Sergei Shtylyov
2007-03-19 19:35 ` YUP
2007-03-20 7:27 ` Albert Lee
2007-03-20 9:07 ` Albert Lee
2007-03-21 4:52 ` Albert Lee
2007-03-21 9:01 ` YUP
2007-03-22 6:06 ` Albert Lee
2007-03-22 7:09 ` Tejun Heo
2007-03-22 12:37 ` Alan Cox
2007-03-23 3:40 ` Albert Lee
2007-03-23 15:19 ` Douglas Gilbert
2007-03-26 5:50 ` Albert Lee
2007-03-22 14:50 ` Sergei Shtylyov
2007-03-23 3:21 ` Albert Lee [this message]
2007-03-19 23:02 ` YUP
2007-03-20 15:23 ` Sergei Shtylyov
2007-03-23 22:13 ` Bartlomiej Zolnierkiewicz
2007-03-26 5:53 ` Albert Lee
2007-03-18 6:42 ` YUP
2007-03-16 22:37 ` YUP
2007-03-17 3:24 ` Albert Lee
2007-03-17 9:09 ` YUP
2007-03-17 10:51 ` Albert Lee
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=4603479D.9070803@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=yupadmin@gmail.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;
as well as URLs for NNTP newsgroup(s).