* Gadiyar, Anand <gadiyar@xxxxxx> [101019 23:21]: > On Wed, Oct 20, 2010 at 5:16 AM, Gadiyar, Anand <gadiyar@xxxxxx> wrote: > > On Wed, Oct 20, 2010 at 5:02 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > >> * Tony Lindgren <tony@xxxxxxxxxxx> [101019 15:48]: > >>> * Gadiyar, Anand <gadiyar@xxxxxx> [101019 11:26]: > >>> > On Tue, Oct 19, 2010 at 11:51 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > >>> > > * Anand Gadiyar <gadiyar@xxxxxx> [101019 07:41]: > >>> > >> Hi all, > >>> > >> > >>> > >> linux-next, as of 20101019, built with the omap2plus_defconfig fails > >>> > >> to boot on omap3 and omap4. (I've disabled CONFIG_ARCH_OMAP2 or > >>> > >> CONFIG_SWP_EMULATE to get the image to build). Building with only > >>> > >> ARCH_OMAP3 allows the resultant image to boot up on OMAP3. Likewise, > >>> > >> an image built with only ARCH_OMAP4 boots up on OMAP4 boards. > >>> > >> > >>> > >> earlyprintk does not provide any additional prints after > >>> > >> "Uncompressing Linux... done, booting the kernel." > >>> > >> > >>> > >> Any ideas where to look? > >>> > > > >>> > > Hmm I did a quick test merge of linux-omap master and rmk/devel > >>> > > branches and that boots just fine. > >>> > > > >>> > > So it's probably something that already got fixed in rmk/devel > >>> > > but is not yet in next, or something that came from elsewhere, > >>> > > or something that we have in omap-testing branch that's not in > >>> > > for-next for some reason. > >>> > > >>> > I tried bisecting linux-next between v2.6.36-rc8 and HEAD, but > >>> > there's a commit in between that breaks the build. I'll take another > >>> > stab at this in a while. > >>> > >>> Looks like current next at 80f8f1f8b33750d954beb386c0c8142d0c01c25c > >>> boots again except on 2430sdp it produces a NULL pointer at ubi_io_write. > >> > >> Oops, sorry it's still broken, wrong tree. > >> > > > > I've started bisecting again - I needed to pick commit 5bac0926121e > > (driver core: platform_bus: allow runtime override of dev_pm_ops) to > > solve the build break. > > > > Will report back if I find something. > > > > I tried disabling CONFIG_SMP and CONFIG_SMP_ON_UP, and the resulting > image booted up just fine. Looks like it's caused by this patch: "ARM: hotplug cpu: Keep processor information, startup code & __lookup_processor_type" It's probably trashing registers it shouldn't. Will take a look and post something to linux-arm-kernel. Tony -- 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
