From: Tero Kristo <t-kristo@ti.com>
To: Kevin Hilman <khilman@linaro.org>,
kernel-build-reports@lists.linaro.org,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
Mike Turquette <mturquette@linaro.org>,
linux-omap <linux-omap@vger.kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: next boot: 34 pass, 5 fail (next-20140122)
Date: Thu, 23 Jan 2014 08:23:37 +0200 [thread overview]
Message-ID: <52E0B569.8000809@ti.com> (raw)
In-Reply-To: <CAGa+x86=gKh11g1pzLqxdimeCxuZ478+ZAxd9GjO-m7Aa8L2fg@mail.gmail.com>
On 01/23/2014 03:35 AM, Kevin Hilman wrote:
> On Wed, Jan 22, 2014 at 4:46 PM, Kevin's boot bot <khilman@linaro.org> wrote:
>> Automated DT boot report for various ARM defconfigs.
>>
>>
>> Tree/Branch: next
>> Git describe: next-20140122
>> Failed boot tests (console logs at the end)
>> ===========================================
>> omap3-tobi,3730storm: FAIL: omap2plus_defconfig
> [...]
>> omap3-tobi,3730storm: FAIL: multi_v7_defconfig
>
> These OMAP3 failures are new regressions. Full failure boot log attached.
> Bisected down to:
>
> cfa9667d4ac9da8b3ba2269f934ecd69ae504d39 is the first bad commit
> commit cfa9667d4ac9da8b3ba2269f934ecd69ae504d39
> Author: Tero Kristo <t-kristo@ti.com>
> Date: Tue Oct 22 11:53:02 2013 +0300
>
> ARM: OMAP2+: io: use new clock init API
>
> clk_init is now separated to a common function which gets called for all
> SoC:s, which initializes the DT clocks and calls the SoC specific
> clock init.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> Acked-by: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Mike Turquette <mturquette@linaro.org>
>
> Kevin
>
Hi,
I think this is because the tobi board is including wrong omap3-soc.dtsi
file (omap34xx.dtsi) through omap3-overo.dtsi.
The board should include omap36xx.dtsi at least based on the boot log:
[ 0.000000] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
-Tero
next prev parent reply other threads:[~2014-01-23 6:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52e06652.c103450a.79d7.6517@mx.google.com>
2014-01-23 1:35 ` next boot: 34 pass, 5 fail (next-20140122) Kevin Hilman
2014-01-23 6:23 ` Tero Kristo [this message]
2014-01-23 8:14 ` Florian Vaussard
2014-01-23 9:00 ` Tero Kristo
2014-01-23 9:15 ` Florian Vaussard
2014-01-23 9:41 ` Florian Vaussard
2014-01-23 12:27 ` Tero Kristo
2014-01-23 16:35 ` Florian Vaussard
2014-01-23 17:33 ` Nishanth Menon
2014-01-24 20:37 ` Florian Vaussard
2014-01-23 17:35 ` Tony Lindgren
2014-01-24 18:00 ` Tony Lindgren
2014-01-24 20:51 ` Florian Vaussard
2014-01-24 18:11 ` Tony Lindgren
2014-01-24 18:13 ` Florian Vaussard
2014-02-05 15:23 ` Kevin Hilman
2014-02-06 8:47 ` Florian Vaussard
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=52E0B569.8000809@ti.com \
--to=t-kristo@ti.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--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).