From: Tony Lindgren <tony@atomide.com>
To: Michael Trimarchi <michael@amarulasolutions.com>
Cc: Casper Lyngesen Mogensen <clmogensen@grundfos.com>,
Ash Charles <ash@gumstix.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP 3630 random crashes
Date: Tue, 1 Jul 2014 00:54:37 -0700 [thread overview]
Message-ID: <20140701075437.GM28884@atomide.com> (raw)
In-Reply-To: <CAOf5uwn_+P5JkU7szHZNj74fqk7ArskiZnYn=eCeamPZ_dWS+g@mail.gmail.com>
* Michael Trimarchi <michael@amarulasolutions.com> [140630 06:49]:
>
> On Mon, Jun 30, 2014 at 3:43 PM, Casper Lyngesen Mogensen
> <clmogensen@grundfos.com> wrote:
> >
> > I got two new Overo AirStorm today, and they have same behavior. I tried disabling
> > the SMSC9xxx again and booted from MMC. This seems to make the backtrace a
> > little more consistent(Tried on both new and old). There is (almost) always something
> > about Alignment trap, the crash log itself differs every time. Also i get to allocate a lot
> > more memory before crash with these settings.
>
> What kernel version are you using?
We should have v3.15 working fine, but PM features are not merged
in util for v3.16.
I would try dding calls to omap_sdrc_init to pdata-quirks.c
the same way board-over.c is doing:
omap_sdrc_init(mt46h32m32lf6_sdrc_params,
mt46h32m32lf6_sdrc_params);
If the memory timings are not correctly set by the bootloader
that could explain the issues.
Regards,
Tony
next prev parent reply other threads:[~2014-07-01 7:54 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
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 [this message]
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=20140701075437.GM28884@atomide.com \
--to=tony@atomide.com \
--cc=ash@gumstix.com \
--cc=clmogensen@grundfos.com \
--cc=linux-omap@vger.kernel.org \
--cc=michael@amarulasolutions.com \
/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).