From: Tejun Heo <htejun@gmail.com>
To: Conke Hu <conke.hu@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, Alan <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ATAPI command TEST_UNIT_READY never succeeds!
Date: Wed, 07 Mar 2007 21:27:32 +0900 [thread overview]
Message-ID: <45EEAFB4.3060306@gmail.com> (raw)
In-Reply-To: <5767b9100703070423y194bf492wad28ddc66ab98775@mail.gmail.com>
Conke Hu wrote:
> On 3/7/07, Conke Hu <conke.hu@gmail.com> wrote:
>> Hi,
>> Do you ever noticed that the ATAPI command TEST_UNIT_READY always
>> fails to execute !?
>> I debugged in the following environments:
>> piix + Intel ICH6/ICH7 PATA
>> atiixp + ATI SB600 PATA
>> libata + ata_piix + Intel ICH6/ICH7 PATA
>> libata + sata_sil24 + Silicon Image 3132
>> libata + ahci + ATI SB600 SATA
>> libata + ahci + Intel AHCI
>> but none of them can execute TEST_UNIT_READY command successfully.
>> For example, in ahci driver, ahci_interrupt() reads port status as
>> 0x4000_0000, which indicates an taskfile error.
> ~~~~~~~~~~~~~~~~~~
>
> 0x4000_0001, not 0x4000_0000, sorry.
>
> more precisely speaking, ahci_host_intr() reads PORT_IRQ_STAT as
> 0x4000_0001, not the expected 0x0000_0001.
I've read your last posting about this, but forgot to follow up. TUR is
supposed to fail if ATAPI device doesn't have media loaded. TUR fails
and sense data returns device not ready - media not present. That's the
normal operation. Does TUR fail even with media loaded or is sense data
not properly fetched?
--
tejun
next prev parent reply other threads:[~2007-03-07 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 12:09 [BUG] ATAPI command TEST_UNIT_READY never succeeds! Conke Hu
2007-03-07 12:23 ` Conke Hu
2007-03-07 12:27 ` Tejun Heo [this message]
2007-03-09 12:21 ` Conke Hu
2007-03-09 12:59 ` Tejun Heo
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=45EEAFB4.3060306@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=conke.hu@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
/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