From: Anand Gadiyar <gadiyar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: linux-next - multi-omap image fails to boot on omap3/4
Date: Fri, 22 Oct 2010 16:15:59 -0400 [thread overview]
Message-ID: <4CC1F0FF.4000701@ti.com> (raw)
In-Reply-To: <20101022185254.GG17595@atomide.com>
On 10/22/2010 2:52 PM, Tony Lindgren wrote:
> * Anand Gadiyar<gadiyar@ti.com> [101022 06:59]:
>> Tony Lindgren wrote:
>>> * Gadiyar, Anand<gadiyar@ti.com> [101019 23:21]:
>>
>> ...
>>
>>>>>>>>>> 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?
>>>>>>>>>
>>
>> ...
>>
>>>>
>>>> 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.
>>>
>>
>> I'm not sure what's going on, but looks like linux-next as of
>> 20101022 boots up fine on panda. I can't explain it, as I couldn't
>> find anything related to the patch you mentioned.
>
> Yeah, it's an alignment issue that's why it sometimes works depending
> on the Kconfig options selected..
>
> For rererence, posted a fix for that at:
>
> https://patchwork.kernel.org/patch/276161/
>
> Tony
The patch seems to work - thanks! Just curious, how do you go about
debugging an issue like this?
- Anand
next prev parent reply other threads:[~2010-10-22 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 14:49 linux-next - multi-omap image fails to boot on omap3/4 Anand Gadiyar
2010-10-19 18:21 ` Tony Lindgren
2010-10-19 18:35 ` Gadiyar, Anand
2010-10-19 22:57 ` Tony Lindgren
2010-10-19 23:32 ` Tony Lindgren
2010-10-19 23:46 ` Gadiyar, Anand
2010-10-20 6:30 ` Gadiyar, Anand
2010-10-21 16:15 ` Tony Lindgren
2010-10-22 14:08 ` Anand Gadiyar
2010-10-22 18:52 ` Tony Lindgren
2010-10-22 20:15 ` Anand Gadiyar [this message]
2010-10-22 21:38 ` Tony Lindgren
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=4CC1F0FF.4000701@ti.com \
--to=gadiyar@ti.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