From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: arm-soc + rmk's tree boot failure on OMAP4430SDP
Date: Fri, 16 Mar 2012 17:47:06 -0700 [thread overview]
Message-ID: <20120317004706.GF7276@atomide.com> (raw)
In-Reply-To: <20120316231158.GA9970@n2100.arm.linux.org.uk>
Hi,
Adding Tomi to this thread.
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120316 16:14]:
> Sometime during the last week, the OMAP4430SDP stopped booting - it now
> stops with no kernel messages output:
>
> http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=69
>
> The previously booted version:
>
> http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=57
>
> worked fine - though this log will only be available for about 3 hours.
>
> I've re-checked my tree, and the OMAP4430SDP boots fine, so it's either
> breakage coming from arm-soc or a result of merging the two trees
> together.
Based on initcall_debug with current linux-next, it seems to hang at
omap_dss_init2. And leaving out CONFIG_OMAP2_DSS makes devices boot
again.
Tomi, can you please investigate?
To reproduce this problem, just set CONFIG_OMAP2_DSS=y in
omap2plus_defconfig, and try to boot. It hangs at least on
blaze and zoom3.
Regards,
Tony
next prev parent reply other threads:[~2012-03-17 0:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 23:11 arm-soc + rmk's tree boot failure on OMAP4430SDP Russell King - ARM Linux
2012-03-17 0:47 ` Tony Lindgren [this message]
2012-03-17 21:15 ` Russell King - ARM Linux
2012-03-19 9:33 ` Tomi Valkeinen
2012-03-19 12:30 ` Russell King - ARM Linux
2012-03-19 12:41 ` Tomi Valkeinen
2012-03-19 12:59 ` Russell King - ARM Linux
2012-03-19 13:02 ` Tomi Valkeinen
2012-03-19 13:59 ` Tomi Valkeinen
2012-03-19 19:21 ` Tony Lindgren
2012-03-22 1:15 ` Russ Dill
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=20120317004706.GF7276@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tomi.valkeinen@ti.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).