From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
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: Wed, 14 Oct 2009 12:53:44 +0100 [thread overview]
Message-ID: <20091014125344.7d0b2597@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <19157.6679.939371.469696@pilspetsen.it.uu.se>
> I guess you didn't see Alan Cox' recent comment about the vt6421:
> <http://marc.info/?l=linux-ide&m=125526699500519&w=2>.
>
> You should probably look for a mini-PCI card with a different chipset.
Docs have appeared - whether they will help tie it down completely I
don't know.
> > -RAID bus controller: VT6421 IDE RAID Controller (rev 50)
> > +IDE interface: VT6421 IDE RAID Controller (rev 50) (prog-if 8f [Master
> > SecP SecO PriP PriO])
That shouldn't matter of itself - its basically header differences
> >
> > - Control: Mem- FastB2B+ ...
> > + Control: Mem+ FastB2B- ...
> >
> > Mem - I guess x86-64 enables it for BIOS access. This is the only PCI
> > device in machine A (ARM).
> >
> > - Latency: 32
> > + Latency: 64
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.
next prev parent reply other threads:[~2009-10-14 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 13:18 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 [this message]
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=20091014125344.7d0b2597@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=khc@pm.waw.pl \
--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
all inboxes | Powered by JetHome®