linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Mudama <edmudama@gmail.com>
To: Michal 'hramrach' Suchanek <hramrach@centrum.cz>
Cc: Brad Campbell <brad@wasp.net.au>,
	f@uvt316-2.ruk.cuni.cz, jgarzik@pobox.com,
	linux-ide@vger.kernel.org
Subject: Re: Via SATA not working here
Date: Tue, 14 Sep 2004 09:03:19 -0600	[thread overview]
Message-ID: <311601c90409140803aaa4d31@mail.gmail.com> (raw)
In-Reply-To: <20040914094336.GG18257@uvt316-2.ruk.cuni.cz>

On Tue, 14 Sep 2004 11:43:36 +0200, Michal 'hramrach' Suchanek
<hramrach@centrum.cz> wrote:
> With 2.6.5 I get the same results.
> 
> The libata error message:
> 
> ata1: DMA timeout, stat 0x0
> ATA: abnormal status 0xD0 on prot 0xEC07
> scsi0: ERROR on channel 0, id0, lin0, CDB: Write (10) 00 01 65 dc e7 00
> 00 42 00
> Current sda: sense key Medium Error
> Additional sense: Write Error - auto reallocation failed
> end_request: I/O error, dev sda, sector 23452903
> ATA: abnormal status 0xD0 on prot 0xEC07
> ATA: abnormal status 0xD0 on prot 0xEC07
> ATA: abnormal status 0xD0 on prot 0xEC07
> 
> Note that the 0xd0 is the same as the ide DMA timeout error.

Not sure how libata queried the additional sense: key/code/qual etc
from the drive, since it appears to have gotten a busy timeout.

FYI, 0xD0 is simply a 0x50 status (ready/seek complete) + the busy
bit, which is automatically set most by hardware upon receipt of a new
command.  In SATA, this is often set internally in a shadow task file
register, and has nothing to do with physical "registers" on the drive
itself.

Can someone quickie translate that CDB for me into its ATA command?

--eric

  reply	other threads:[~2004-09-14 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-12 19:15 Via SATA not working here Michal 'hramrach' Suchanek
2004-09-13  4:23 ` Brad Campbell
2004-09-14  9:43   ` Michal 'hramrach' Suchanek
2004-09-14 15:03     ` Eric Mudama [this message]
2004-09-14 17:54       ` Michal 'hramrach' Suchanek
2004-09-14 18:06         ` Jeff Garzik
2004-09-14 19:57           ` Brad Campbell
2005-02-05 15:03             ` Michal 'hramrach' Suchanek
2005-02-05 15:33               ` Stefan Smietanowski
2005-02-05 23:41                 ` Michal 'hramrach' Suchanek
2004-09-14 20:15           ` Via SATA already working here [was: not working] Michal 'hramrach' Suchanek

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=311601c90409140803aaa4d31@mail.gmail.com \
    --to=edmudama@gmail.com \
    --cc=brad@wasp.net.au \
    --cc=f@uvt316-2.ruk.cuni.cz \
    --cc=hramrach@centrum.cz \
    --cc=jgarzik@pobox.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 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).