linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 15:09:26 -0400	[thread overview]
Message-ID: <46E98AE6.5010003@rtr.ca> (raw)
In-Reply-To: <46E98A5E.8080109@rtr.ca>

> 
>> 14:26:48 root: writing
>> 14:26:54 kernel: qc_issue: CDB 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 14:26:54 kernel: qc_issue_prot: CDB 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 14:26:54 kernel: qc_issue: CDB 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 14:26:54 kernel: qc_issue_prot: CDB 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 14:26:54 kernel: qc_issue: CDB 03 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
>> 14:26:54 kernel: qc_issue_prot: CDB 03 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00
>> 14:26:54 kernel: ata3: DRQ=1 with device error, dev_stat 0x59
>> 14:26:54 kernel: st0: Sense Key : Illegal Request [current]
>> 14:26:54 kernel: st0: Add. Sense: Invalid command operation code
> 
> 
> One more bit of possibly helpful information here.
> 
> The last time I wrote a working ATAPI Tape driver,
> it always translated SCSI opcode 0x05 (READ_BLOCK_LIMITS) into MODE_SENSE.
> 
> I don't remember why it did that, but it was necessary at the time.
> So I wonder if the error above has anything to do with the READ_BLOCK_LIMITS
> command that can be seen just above the TEST_UNIT_READY and REQUEST_SENSE CDBs ?

Ah.. my notes to myself from that era say:

 // ATAPI tape drives do not implement the "READ_BLOCK_LIMITS" command,
 // but the same information can be obtained from a MODE_SENSE instead.
 // So here we emulate the former, using the latter.

Cheers

  reply	other threads:[~2007-09-13 19:09 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
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 [this message]
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=46E98AE6.5010003@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 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).