From: Robert Hancock <hancockrwd@gmail.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sata_via: SError: { UnrecovData Proto TrStaTrns }
Date: Mon, 05 Oct 2009 19:58:40 -0600 [thread overview]
Message-ID: <4ACAA450.6030405@gmail.com> (raw)
In-Reply-To: <m3my46yo5g.fsf@intrepid.localdomain>
On 10/05/2009 07:18 AM, Krzysztof Halasa wrote:
> Hi,
>
> What could that be?
> VIA VT6421A mini-PCI card and SATA SSD from Transcend. IXP425 (ARM)
> little-endian CPU. 128 MB RAM - VT6421A can access only the first 64 MB
> of system RAM, but there is bounce buffering (a la swiotlb) for the
> rest.
>
> Sometimes it produces:
>
> ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6
> ata1.00: BMDMA stat 0x5
> ata1: SError: { UnrecovData Proto TrStaTrns }
> ata1.00: cmd c8/00:20:b7:18:38/00:00:00:00:00/e0 tag 0 dma 16384 in
> res 51/40:20:b7:18:38/00:00:00:00:00/e0 Emask 0x12 (ATA bus error)
> ata1.00: status: { DRDY ERR }
> ata1.00: error: { UNC }
> ata1: hard resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.00: configured for UDMA/100
> ata1: EH complete
>
> Any ideas?
Presumably a SATA bus communication error. Are you sure the SATA
connections and cable are good?
next prev parent reply other threads:[~2009-10-06 1:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 13:18 sata_via: SError: { UnrecovData Proto TrStaTrns } Krzysztof Halasa
2009-10-05 14:37 ` Mikael Pettersson
2009-10-06 18:21 ` Krzysztof Halasa
2009-10-06 1:58 ` Robert Hancock [this message]
2009-10-06 18:22 ` Krzysztof Halasa
2009-10-06 16:26 ` Mikael Pettersson
2009-10-06 18:49 ` Krzysztof Halasa
2009-10-13 23:18 ` Krzysztof Halasa
2009-10-14 0:16 ` Krzysztof Halasa
2009-10-14 0:23 ` Mikael Pettersson
2009-10-14 11:53 ` Alan Cox
2009-10-20 16:00 ` Krzysztof Halasa
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=4ACAA450.6030405@gmail.com \
--to=hancockrwd@gmail.com \
--cc=khc@pm.waw.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).