Recent OMAP git broken on Beagle

Recent OMAP git broken on Beagle

[Dirk Behme]

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?

Many thanks

Dirk

[1] http://source.mvista.com/git/?p=linux-omap-2.6.git;a=summary

Re: Recent OMAP git broken on Beagle

[Tony Lindgren]

* 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

Re: Recent OMAP git broken on Beagle

[Dirk Behme]

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

Re: Recent OMAP git broken on Beagle

[Paul Walmsley]

Hello Dirk,

On Sat, 10 May 2008, Dirk Behme wrote:

> -- 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

Curious, this boots fine on 3430sdp, and there's nothing in that patch 
that should affect Beagle in particular.  

Could you try building cdda2a9adbc5421f4857e0313afc6c189f422e25 and see if 
that also breaks?  Of the recent OMAP-specific patches, that's the one 
that I would suspect.  And if that also breaks, maybe try the one 
before it, 352b2e24c5cd193a40ae376fec85665f2660aeb1 ?


- Paul

Re: Recent OMAP git broken on Beagle

[Dirk Behme]

Paul Walmsley wrote:
> Hello Dirk,
> 
> On Sat, 10 May 2008, Dirk Behme wrote:
> 
> 
>>-- 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
> 
> 
> Curious, this boots fine on 3430sdp, and there's nothing in that patch 
> that should affect Beagle in particular.  
> 
> Could you try building cdda2a9adbc5421f4857e0313afc6c189f422e25 and see if 
> that also breaks?  

Hmm, I think cdda2a9a... was the first one working for me:

http://marc.info/?l=linux-omap&m=121040218707239&w=2

I started with  "git bisect good cdda2a9a..."

If you like, I can recheck again. But would be better if anybody else 
could confirm this, just in case I missed anything. Hint, hint ;)

> Of the recent OMAP-specific patches, that's the one 
> that I would suspect.  And if that also breaks, maybe try the one 
> before it, 352b2e24c5cd193a40ae376fec85665f2660aeb1 ?

In a private mail I got:

-- cut --
To add another data point:  on the OMAP3 EVM warm boots fail as 
described, but cold boots complete successfully.
-- cut --

Unfortunately, he couldn't confirm which commit is failing for him yet.

On Beagle we currently boot using bootrom starting from MMC. Like with 
TWL, it seems that the pre-initialization by bootrom has some 
influence on kernel behaviour.

Thanks

Dirk

Re: Recent OMAP git broken on Beagle

[Paul Walmsley]

On Tue, 13 May 2008, Dirk Behme wrote:

> If you like, I can recheck again. But would be better if anybody else could
> confirm this, just in case I missed anything. Hint, hint ;)

I would love to help, but, no Beagle here :-(

> In a private mail I got:
> 
> -- cut --
> To add another data point:  on the OMAP3 EVM warm boots fail as described, but
> cold boots complete successfully.
> -- cut --
> 
> Unfortunately, he couldn't confirm which commit is failing for him yet.

very interesting...


- Paul