From: "Cousson, Benoit" <b-cousson@ti.com>
To: Aaro Koskinen <aaro.koskinen@nokia.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tarun Kanti DebBarma <tarun.kanti@ti.com>
Subject: Re: Code for v2.6.39 merge window frozen, patches archived
Date: Tue, 15 Mar 2011 21:07:41 +0100 [thread overview]
Message-ID: <4D7FC70D.7050508@ti.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1103151856180.880@esdhcp041196.research.nokia.com>
Hi Aaro,
On 3/15/2011 6:54 PM, Aaro Koskinen wrote:
> Hi,
>
> On Mon, 14 Mar 2011, Tony Lindgren wrote:
>> I've applied few random fix like patches today into omap-for-linus
>> but that's it for this merge window.
>>
>> So let's do some testing with with Stephen's for-next and
>> omap-for-linus and start queueing up fixes for the -rc cycle.
>
> I did some quick testing:
>
> linux-omap/master, omap2plus_defconfig:
>
> - RM-680 hangs after uncompressing kernel. earlyprintk shows:
>
> [ 0.293395] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_core
> [ 0.300903] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per
> [ 0.308288] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup
> [ 0.316101] omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck.
>
> (then some garbage)
>
> - With RX-51 I get the same messages, but no hang.
Mmm, that looks like an access to a secure timer from hwmod code on a HS
device. Could you comment out the timer12 entry
(&omap3xxx_timer12_hwmod) in the omap3 hwmod list at the end of
omap_hwmod_3xxx_data.c to check that?
Thanks
Benoit
>
> omap-for-linux, omap2plus_defconfig:
>
> - Pretty much the same. RM-680 hangs and the first bad commit is
> ce722d269ff85ab11aa680784bcc6eff06e3e3ea and earlyprintk shows
> "external abort on non-linefetch" in omap_hwmod_read() after
> above messages.
>
> Mainline kernel (v2.6.38) boots fine.
>
> A.
> --
> 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
next prev parent reply other threads:[~2011-03-15 20:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:25 Code for v2.6.39 merge window frozen, patches archived Tony Lindgren
2011-03-15 3:05 ` Nishanth Menon
2011-03-15 15:09 ` Kevin Hilman
2011-03-15 15:20 ` Menon, Nishanth
2011-03-15 17:54 ` Aaro Koskinen
2011-03-15 20:07 ` Cousson, Benoit [this message]
2011-03-15 20:32 ` aaro.koskinen
2011-03-16 13:49 ` Aaro Koskinen
2011-03-16 14:33 ` Cousson, Benoit
2011-03-16 15:32 ` Tony Lindgren
2011-03-16 17:26 ` Aaro Koskinen
2011-03-16 17:10 ` Aaro Koskinen
2011-03-29 23:32 ` Tony Lindgren
2011-03-30 15:23 ` Kevin Hilman
2011-03-31 14:53 ` Aaro Koskinen
2011-04-02 2:42 ` Nicolas Pitre
2011-04-13 14:04 ` Tony Lindgren
2011-04-13 14:34 ` Aaro Koskinen
2011-04-15 13:41 ` Jarkko Nikula
2011-04-13 14:49 ` Nicolas Pitre
2011-04-13 15:09 ` Tony Lindgren
2011-04-19 10:13 ` Tony Lindgren
2011-04-19 13:27 ` Nicolas Pitre
2011-04-19 14:15 ` Tony Lindgren
2011-03-16 14:07 ` G, Manjunath Kondaiah
2011-03-16 14:20 ` G, Manjunath Kondaiah
2011-03-16 14:39 ` Kishore Kadiyala
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=4D7FC70D.7050508@ti.com \
--to=b-cousson@ti.com \
--cc=aaro.koskinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tarun.kanti@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).