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@xxxxxxxxx>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
