From: Jeroen Hofstee <linux-arm@myspectrum.nl>
To: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: OMAP baseline test results for v4.1-rc5
Date: Mon, 01 Jun 2015 00:15:51 +0200 [thread overview]
Message-ID: <556B8817.7080305@myspectrum.nl> (raw)
In-Reply-To: <5569DDB3.2040802@myspectrum.nl>
Hi,
On 30-05-15 17:56, Jeroen Hofstee wrote:
> Hello Paul,
>
> On 30-05-15 17:50, Paul Walmsley wrote:
>> Here are some basic OMAP test results for Linux v4.1-rc5.
>> Logs and other details at:
>>
>> http://www.pwsan.com/omap/testlogs/test_v4.1-rc5/20150529162206/
>>
>
> The cmt3517 seems to have these some In-Band errors.
> Do you happen to know where these are coming from?
>
git bisect + some workarounds seem to indicate:
d744ce37b721d6678f420ba0fb058f615eb015b6 is the first bad commit
commit d744ce37b721d6678f420ba0fb058f615eb015b6
Author: Tero Kristo <t-kristo@ti.com>
Date: Tue Feb 24 16:22:45 2015 +0200
ARM: dts: omap3: add minimal l4 bus layout with control module support
This patch creates an l4_core interconnect for OMAP3, and moves some
of the generic peripherals under it. System control module nodes are
moved under this new interconnect also, and the SCM clock layout
is changed to use the renamed SCM node as the clock provider.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
Reported-by: Tony Lindgren <tony@atomide.com>
I haven't looked further into it yet,
Regards, Jeroen
next prev parent reply other threads:[~2015-05-31 22:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 15:50 OMAP baseline test results for v4.1-rc5 Paul Walmsley
2015-05-30 15:56 ` Jeroen Hofstee
2015-05-31 22:15 ` Jeroen Hofstee [this message]
2015-06-01 5:49 ` Paul Walmsley
2015-06-01 15:29 ` Tero Kristo
2015-06-01 15:30 ` [PATCH] ARM: dts: AM35xx: fix system control module clocks Tero Kristo
2015-06-01 16:56 ` Jeroen Hofstee
2015-06-01 17:31 ` Tony Lindgren
2015-06-01 17:44 ` Paul Walmsley
2015-06-01 18:04 ` Tony Lindgren
2015-06-01 18:06 ` Tony Lindgren
2015-06-01 21:26 ` Paul Walmsley
2015-06-02 7:15 ` Tero Kristo
2015-06-01 21:21 ` Paul Walmsley
2015-06-01 18:04 ` Tero Kristo
2015-06-05 8:01 ` Jeroen Hofstee
2015-06-05 8:04 ` Jeroen Hofstee
2015-06-07 9:41 ` Jeroen Hofstee
2015-06-07 19:56 ` Paul Walmsley
2015-06-08 2:38 ` Paul Walmsley
2015-06-08 22:00 ` Jeroen Hofstee
2015-06-08 21:43 ` Jeroen Hofstee
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=556B8817.7080305@myspectrum.nl \
--to=linux-arm@myspectrum.nl \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).