From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chuck Ebbert <cebbert@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
craig48@swbell.net
Subject: Re: ATAPI tape drives broken with libata
Date: Thu, 13 Sep 2007 12:35:14 -0400 [thread overview]
Message-ID: <46E966C2.1050405@rtr.ca> (raw)
In-Reply-To: <20070831151903.37a60ba9@the-village.bc.nu>
Alan Cox wrote:
> On Thu, 30 Aug 2007 12:11:39 -0400
> Chuck Ebbert <cebbert@redhat.com> wrote:
>
>> On 08/29/2007 07:50 PM, Alan Cox wrote:
>>> Device Ready, Seek Complete, Data Request, Error
>>>
>>> DRQ and Error together is a bit odd to say the least
>>>
>>> It then commits suicide and falls off the bus. That may be due to the
>>> fact we use SRST on ATAPI device errors still rather than trying an ATAPI
>>> reset first. Shouldn't matter though.
>>>
>>> Since you are the lucky owner of the object in question can you dump the
>>> contents of the packet command going to the device when this occurs ?
>>>
>> I don't have it, it's a Fedora user. Maybe I should ask Mark Lord if he'll
>> send me the one he has.
>>
>> IAC how do I dump the packet? Use ata_scsi_dump_cdb()?
>
> Yep - if the command issued is a packet command the cdb is 12-16 bytes of
> SCSI command block.
More or less the same behaviour is observed here with the Conner ATAPI tape unit
that I (still!) have on the shelf.
I'll see about instrumenting things for more info. It really sucks as is, though! :)
Cheers
next prev parent reply other threads:[~2007-09-13 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 22:55 ATAPI tape drives broken with libata Chuck Ebbert
2007-08-29 23:50 ` Alan Cox
2007-08-30 16:11 ` Chuck Ebbert
2007-08-31 14:19 ` Alan Cox
2007-09-13 16:35 ` Mark Lord [this message]
2007-09-13 18:22 ` Mark Lord
2007-09-13 18:42 ` Mark Lord
2007-09-13 19:07 ` Mark Lord
2007-09-13 19:09 ` Mark Lord
2007-09-19 20:50 ` Alan Cox
2007-09-22 0:28 ` Mark Lord
2007-09-21 3:07 ` Albert Lee
2007-08-30 4:00 ` Jeff Garzik
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=46E966C2.1050405@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=craig48@swbell.net \
--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.