From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: "Foster, Doug F" <doug.f.foster@intel.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: ATAPI question
Date: Sun, 01 Mar 2009 21:51:48 +0900 [thread overview]
Message-ID: <49AA84E4.3050108@kernel.org> (raw)
In-Reply-To: <49A8AAC6.2090201@gmail.com>
Hello,
Robert Hancock wrote:
>> Using a SATA analyzer, I find that on an INQUIRY (12h) ATAPI packet
>> command, the device sets bit-6 (DRDY) and bit-4 (SERV) in the status
>> register, and bits 0 (CoD) and 1 (IO) are set in the ATAPI Interrupt
>> Reason Register (ATA Sector Count Register). After SERVICE is flagged
>> by the ATAPI device (and not serviced), it doesn't respond properly
>> from then on.
>
> Bit 4 isn't SERV in this context, it's DRQ. (It's only SERV when TCQ is
> in use, which it isn't.) It looks like this is a READ CAPACITY command
> that's being issued by PIO. DRQ means the device expects to transfer
> data - either to receive the CDB or send the response. Presumably that
> didn't happen for some reason. Are you sure about both the C/D and I/O
> bits being 1? That would mean command transfer to the host, which
> doesn't make any sense.
>
> You're saying that DRQ never gets cleared after the INQUIRY command?
> It's possible the device wanted to transfer more data than the PRD table
> had room for. Not sure what AHCI ends up doing in this case. I'm CCing
> Tejun who might know more..
libata always prepares for extra space for draining so I doubt that.
Any chance you can post the traces?
--
tejun
next prev parent reply other threads:[~2009-03-01 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 23:50 ATAPI question Foster, Doug F
2009-02-28 3:08 ` Robert Hancock
2009-03-01 12:51 ` Tejun Heo [this message]
2009-03-02 15:58 ` Foster, Doug F
2009-03-02 21:50 ` Foster, Doug F
2009-03-03 0:35 ` Tejun Heo
2009-03-03 15:44 ` Foster, Doug F
2009-03-03 18:19 ` Foster, Doug F
2009-03-04 1:44 ` Tejun Heo
2009-03-04 2:09 ` Robert Hancock
2009-03-04 15:44 ` Foster, Doug F
2009-03-04 16:03 ` Tejun Heo
2009-03-09 21:35 ` Foster, Doug F
2009-03-11 9:31 ` Tejun Heo
2009-03-12 21:02 ` Foster, Doug F
2009-03-02 23:33 ` Robert Hancock
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=49AA84E4.3050108@kernel.org \
--to=tj@kernel.org \
--cc=doug.f.foster@intel.com \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@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 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.