From: Krzysztof Halasa <khc@pm.waw.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Robert Hancock <hancockrwd@gmail.com>
Subject: Re: sata_via: SError: { UnrecovData Proto TrStaTrns }
Date: Tue, 20 Oct 2009 18:00:40 +0200 [thread overview]
Message-ID: <m33a5e5a3b.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20091014125344.7d0b2597@lxorguk.ukuu.org.uk> (Alan Cox's message of "Wed, 14 Oct 2009 12:53:44 +0100")
Update: I've connected Kingston SSD instead of Transcend's. The same
errors appear, but now there is a lot of them (> 30 instead of maybe 5
per my test with Transcend).
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> These two may be worth playing with, especially latency. Forcing the
> latency on the problem board would be interesting given that it is a DMA
> transfer that is failing.
Changing the latency byte doesn't seem to change anything. OTOH the
VT6421A mini-PCI card is the only PCI device in system (not counting the
on-CPU AHB-PCI bridge). The problem is also present (to a lesser extent)
when I plug it into x86-64 machine (using mini-PCI adapter). The SSD
works fine if connected to motherboard's NVidia MCP55 SATA controller.
I have read the datasheet and tried some changes to PCI registers but it
doesn't fix it.
I'm going to test x86-64 + VT6421A + Kingston SSD combination soon.
Unfortunately I don't have a (mini) PCI analyser... I will look at
REQ/GNT and similar signals on PCI, though.
--
Krzysztof Halasa
prev parent reply other threads:[~2009-10-20 16:00 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
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 [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=m33a5e5a3b.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).