linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eric A. Cottrell" <eac@shore.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: LIBATA AHCI engine timeout hang with ATAPI devices
Date: Thu, 14 Apr 2005 22:54:29 -0400	[thread overview]
Message-ID: <425F2CE5.2010904@shore.net> (raw)
In-Reply-To: <42570F07.6080406@shore.net>

Hello,

I made some progress fixing ATAPI problems even with my system being down a few days due to a video card failure.

One ATAPI problem area is the lack of filling the sense buffer when there is an error.  There are ata to scsi mapping functions for 
hard drives but nothing for ATAPI.  The SCSI system sends some commands that are not supported by ATAPI so an illegal request sense 
key should be sent up from the driver.

I recently noticed the docs for the PACKET command said that ATAPI devices return error information in the task file.  One of the 
bytes looks like information in the third byte of the sense information.  I added a function that translated the ATAPI error 
information into a basic SCSI sense block without any additional sense information.

Using the AHCI driver I do see valid sense information.  The request luns command returns a illegal request as it is not supported 
by the drive.  The ata_piix driver always returned a zero for the sense.  I need to do some more work to fix it and other problems.

73 Eric  eac@shore.net

      reply	other threads:[~2005-04-15  2:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 18:47 LIBATA AHCI engine timeout hang with ATAPI devices Eric A. Cottrell
2005-04-08 19:13 ` [PATCH] " Jeff Garzik
2005-04-08 23:08   ` Eric A. Cottrell
2005-04-15  2:54     ` Eric A. Cottrell [this message]

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=425F2CE5.2010904@shore.net \
    --to=eac@shore.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).