From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: 3.11-rc1: OMAP3630 boot crash
Date: Mon, 29 Jul 2013 23:38:56 +0300 [thread overview]
Message-ID: <20130729203856.GB30725@blackmetal.musicnaut.iki.fi> (raw)
In-Reply-To: <alpine.DEB.2.02.1307290809200.30864@utopia.booyaka.com>
On Mon, Jul 29, 2013 at 08:11:39AM +0000, Paul Walmsley wrote:
> On Thu, 25 Jul 2013, Aaro Koskinen wrote:
>
> > On Tue, Jul 16, 2013 at 07:58:34PM +0300, Aaro Koskinen wrote:
> > > I get the following boot crash on N950/RM-680 (3630) with unpatched
> > > 3.11-rc1. The crash looks specific to 3630 (it happens during
> > > omap3630_init_late), also the same kernel binary works with N900/RX-51
> > > (3430). You can find the .config after the crash.
> >
> > I put a debug print to _omap_hwmod_mux_handle_irq
> > (omap_hwmod_mux_scan_wakeups), and it seems when the crash happens the
> > pad name is always "uart3_rx_irrx.uart3_rx_irrx". I made another hack
> > and just "continue" if the pad name is this, and the crash is gone.
> >
> > Any ideas?
>
> Nothing comes to mind, but it's worth mentioning that this doesn't happen
> on the 37xx EVM here. So it's probably RM-680-specific.
Probably timing specific... I enabled CONFIG_DEBUG_FS and the crash
went away.
A.
prev parent reply other threads:[~2013-07-29 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 16:58 3.11-rc1: OMAP3630 boot crash Aaro Koskinen
2013-07-24 22:57 ` Aaro Koskinen
2013-07-29 8:11 ` Paul Walmsley
2013-07-29 20:38 ` Aaro Koskinen [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=20130729203856.GB30725@blackmetal.musicnaut.iki.fi \
--to=aaro.koskinen@iki.fi \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.