From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>, beagleboard@googlegroups.com
Subject: Re: Recent OMAP git broken on Beagle
Date: Sat, 10 May 2008 21:19:30 +0200 [thread overview]
Message-ID: <4825F542.1040906@googlemail.com> (raw)
In-Reply-To: <20080510180935.GA8121@atomide.com>
Tony Lindgren wrote:
> * 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?
-- cut --
> git bisect bad
757f0b4ad6b0fd4377c2ee512fc595b5778aa3ac is first bad commit
commit 757f0b4ad6b0fd4377c2ee512fc595b5778aa3ac
Author: Paul Walmsley <paul@pwsan.com>
Date: Fri May 9 14:45:24 2008 -0700
powerdomain: convert pwrdm_mutex to rwsem
Convert pwrdm_mutex to pwrdm_rwsem to avoid trying to relock
mutex in the
event that the pwrdm_for_each() callback function calls something
that
triggers a pwrdm_lookup(). Problem found by Jouni Högander
<jouni.hogander@nokia.com>
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
:040000 040000 833450098951bb58b4753d0ec641e8b1e767c419
eb7329d713ff74ae46d0a8145f80cd4a259b8fc8 M arch
-- cut --
http://source.mvista.com/git/?p=linux-omap-2.6.git;a=commitdiff;h=757f0b4ad6b0fd4377c2ee512fc595b5778aa3ac
Anybody with Beagle can confirm this?
Many thanks
Dirk
--
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 19:19 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
2008-05-10 19:19 ` Dirk Behme [this message]
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=4825F542.1040906@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=beagleboard@googlegroups.com \
--cc=linux-omap@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox