From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: select required CPU and L2 errata options
Date: Fri, 06 Jan 2012 19:36:37 +0100 [thread overview]
Message-ID: <4535343.dMzhSsBukX@ax5200p> (raw)
In-Reply-To: <20230.64932.51663.410120@pilspetsen.it.uu.se>
On Friday 06 January 2012 14:56:52 Mikael Pettersson wrote:
> Marc Dietrich writes:
> > On Thursday 05 January 2012 10:40:48 Doug Anderson wrote:
> > > I can't comment on the L2 stuff (haven't looked there), but just
> > > going
> > > by Cortex-A9 revisions (T25 has roughly r1p1 and T30 has r2p7),
> > > I've
> > > got this table:
> > >
> > > Errata T25 (A9 ~r1p1) T30 (A9 r2p7) Applies to
> > > ARM_ERRATA_364296 pre A8
> > > ARM_ERRATA_411920 pre A8
> > > ARM_ERRATA_430973 A8
> > > ARM_ERRATA_458693 A8
> > > ARM_ERRATA_460075 A8
> > > ARM_ERRATA_720789 yes A9 (prior to
> > > r2p0) ARM_ERRATA_742230 yes A9
> > > (r1p0..r2p2) ARM_ERRATA_742231
> > > A9 (r2p0..r2p2) ARM_ERRATA_743622
> > > A9 (r2p0..r2p2) ARM_ERRATA_751472 yes yes
> > > A9 (prior to r3p0) ARM_ERRATA_754322 yes
> > > A9 (r2p*, r3p*) ARM_ERRATA_754327 yes
> > > A9 (prior to r2p0) ARM_ERRATA_764369 yes
> > > yes A9 MPCore (all revs)
> > >
> > > ...so that means we should also be adding in 720789 (T2x), 751472
> > > (T2x, T30), 754322 (T30), 754327 (T2x), 764369 (T2x, T30).
> >
> > AFAIK, 720789 (TLBIASIDIS and TLBIMVAIS operations can broadcast a
> > faulty ASID) is fixed in userspace (or gcc) nowadays (at least in
> > Ubuntu) so I think this can be neglected.
>
> Not everyone uses Ubuntu.
yeah, I know. I just said this because nvidias reference filesystem is based
upon it.
> Can you provide a reference to the corresponding gcc and/or Ubuntu patch?
all I found in the haste is
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/739374
I think in the end gcc was patched not emit get/set_tls syscalls but to use
MCR/MRC cp15 ops (sorry, I don't know what this means - just copied from irc
log). This meant that the whole userspace needed recompilation. It is possible
that all newer gcc behave like this. As far as I understood, enabling the
erratum in the kernel with fixed userspace will make the problem reapear.
Someone with more knowledge may correct me.
> (I got a Tegra-2 based trimslice last summer, but it's been completely
> unreliable under load (hangs hard during "make -j2" gcc bootstraps),
> hence I'm looking for patches or any other information that can help
> me fix or work around whatever bugs it has.)
I think this can't be related to the erratum above because it manifestated
itself in a segfault or illegal instruction userspace error.
Did you tried to ask in the trimslice forum about this error?
Marc
next prev parent reply other threads:[~2012-01-06 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 23:29 [PATCH] ARM: tegra: select required CPU and L2 errata options Olof Johansson
2012-01-05 16:30 ` Marc Dietrich
2012-01-05 18:40 ` Doug Anderson
2012-01-05 22:03 ` Marc Dietrich
2012-01-06 13:56 ` Mikael Pettersson
2012-01-06 18:36 ` Marc Dietrich [this message]
2012-01-05 18:46 ` Stephen Warren
-- strict thread matches above, loose matches on Subject: below --
2012-02-14 20:39 Stephen Warren
2012-02-26 22:25 ` Olof Johansson
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=4535343.dMzhSsBukX@ax5200p \
--to=marvin24@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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