From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap@vger.kernel.org, beagleboard@googlegroups.com
Subject: Re: Recent OMAP git broken on Beagle
Date: Sat, 10 May 2008 11:09:36 -0700 [thread overview]
Message-ID: <20080510180935.GA8121@atomide.com> (raw)
In-Reply-To: <48254562.7000006@googlemail.com>
* Dirk Behme <dirk.behme@googlemail.com> [080509 23:49]:
>
> I tried latest OMAP git (2.6.26-rc1-omap1, git from today, HEAD ==
> 42fa072e237427675752bb9da05bf406bff19719, "OMAP3 EVM: enable ethernet
> support") on OMAP3 based BeagleBoard and it immediately stops after
> output of Kernel command line (with CONFIG_DEBUG_LL enabled):
>
> ...
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
> <5>Kernel command line: console=ttyS2,115200n8 ...
>
> No later output or crash, nothing.
>
> On an older 2.6.25-omap1 kernel next output is
>
> ...
> Kernel command line: console=ttyS2,115200n8 ...
> Clocking rate (Crystal/DPLL/ARM core): 26.0/266/381 MHz
> GPMC revision 5.0
> ...
>
> Assuming that it might be related to recent clock or powerdomain changes
> [1] I switched back to HEAD == "Fix remaining sparse warnings in
> arch/arm/mach-omap2" (git-checkout
> cdda2a9adbc5421f4857e0313afc6c189f422e25) and system now boots again.
>
> Any idea?
Can you try git-bisect to see which one breaks booting on beagle?
Tony
> Many thanks
>
> Dirk
>
> [1] http://source.mvista.com/git/?p=linux-omap-2.6.git;a=summary
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-05-10 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 6:49 Recent OMAP git broken on Beagle Dirk Behme
2008-05-10 18:09 ` Tony Lindgren [this message]
2008-05-10 19:19 ` Dirk Behme
2008-05-12 20:30 ` Paul Walmsley
2008-05-13 17:37 ` Dirk Behme
2008-05-13 17:41 ` Paul Walmsley
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=20080510180935.GA8121@atomide.com \
--to=tony@atomide.com \
--cc=beagleboard@googlegroups.com \
--cc=dirk.behme@googlemail.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