From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@ti.com>,
linux-omap@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>
Subject: Re: boot hang using OMAP for-next + Russell's for-linus
Date: Mon, 30 May 2011 18:58:36 +0530 [thread overview]
Message-ID: <4DE39B84.40003@ti.com> (raw)
In-Reply-To: <20110530080533.GF11352@atomide.com>
Tony,
On 5/30/2011 1:35 PM, Tony Lindgren wrote:
> * Kevin Hilman<khilman@ti.com> [110527 14:24]:
>> FYI... I just found this, but won't be able to look into it until next
>> week, so if anyone needs a weekend debug project...
>>
>> Using Tony's for-next branch, I'm able to boot an omap2plus_defconfig (+
>> busybox initramfs) kernel on my 3430/n900 just fine. I then tried to
>> merge in Russell's for-linus branch and it hangs during boot.
>>
>> It appears to hang in the init/registration of i2c busses. Commenting
>> out the i2c bus registration from board-rx51-peripherals and disabling a
>> few of the users of i2c, I was able to boot.
>
> Looks like at least v3.0-rc1 boots just fine, so whatever that was
> has been already fixed.
>
I noticed couple of issues with v3.0-rc1 as reported [1]
on OMAP4430 SDP. Am I missing any trick for the console issue.
Regards
Santosh
[1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg50126.html
next prev parent reply other threads:[~2011-05-30 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 21:27 boot hang using OMAP for-next + Russell's for-linus Kevin Hilman
2011-05-30 8:05 ` Tony Lindgren
2011-05-30 13:28 ` Santosh Shilimkar [this message]
2011-05-31 16:13 ` Kevin Hilman
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=4DE39B84.40003@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.