From: Tony Lindgren <tony@atomide.com>
To: Casper Lyngesen Mogensen <clmogensen@grundfos.com>
Cc: Ash Charles <ash@gumstix.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP 3630 random crashes
Date: Mon, 23 Jun 2014 01:35:12 -0700 [thread overview]
Message-ID: <20140623083512.GC28884@atomide.com> (raw)
In-Reply-To: <1403503623834.68421@grundfos.com>
* Casper Lyngesen Mogensen <clmogensen@grundfos.com> [140622 23:08]:
> Hi again
>
> All my boards are marked "JW513". So the problem might be hardware related, i will try to get some new Overo's and test on these instead.
OK, please let us know how it goes.
Also if using armhf based distro some omap3 SoCs need
CONFIG_CPU_BPREDICT_DISABLE=y or CONFIG_ARM_ERRATA_430973=y
or both. Sorry no idea yet which revisions, but I've seen some
flakeyness with apt-get dist-upgrade occasionally failing
on a 3630 with revision info:
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5307d
Regards,
Tony
next prev parent reply other threads:[~2014-06-23 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 8:50 OMAP 3630 random crashes Casper Lyngesen Mogensen
2014-06-20 9:14 ` Tony Lindgren
2014-06-20 14:00 ` Casper Lyngesen Mogensen
2014-06-20 14:17 ` Ash Charles
2014-06-20 14:26 ` Casper Lyngesen Mogensen
2014-06-23 6:07 ` Casper Lyngesen Mogensen
2014-06-23 8:35 ` Tony Lindgren [this message]
2014-06-30 13:43 ` Casper Lyngesen Mogensen
2014-06-30 13:47 ` Michael Trimarchi
2014-06-30 14:01 ` Casper Lyngesen Mogensen
2014-07-01 7:54 ` Tony Lindgren
2014-07-01 10:35 ` Casper Lyngesen Mogensen
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=20140623083512.GC28884@atomide.com \
--to=tony@atomide.com \
--cc=ash@gumstix.com \
--cc=clmogensen@grundfos.com \
--cc=linux-omap@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).