From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@linaro.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Russell King <rmk+kernel@arm.linux.org.uk>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-next <linux-next@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
Date: Fri, 5 Dec 2014 10:13:51 -0600 [thread overview]
Message-ID: <5481D9BF.2090007@ti.com> (raw)
In-Reply-To: <5481D913.9040109@ti.com>
On 12/05/2014 10:10 AM, Nishanth Menon wrote:
> next-20141204 fails to boot, but next-20141203 boots fine with
> omap2plus_defconfig.
>
> Panda-ES(4460):
> https://github.com/nmenon/kernel-test-logs/blob/next-20141204/omap2plus_defconfig/pandaboard-es.txt
> Panda(4430):
> https://github.com/nmenon/kernel-test-logs/blob/next-20141204/omap2plus_defconfig/pandaboard-vanilla.txt
>
> at the point of hang (JTAG):
> pandaboard-es:
> cpu0: http://slexy.org/view/s2eIFqkRd5
> cpu1: http://slexy.org/view/s2Tysb6gpL
>
> Case #1:
> Disabling CPUIDLE allows boot to proceed. there does not seem to have
> been any change in drivers/cpuidle and arch/arm/mach-omap2 w.r.t this.
>
> Case #2: Reverting the following allows boot.
>
> From next-20141204
> 10df7d5 ARM: 8211/1: l2c: Add support for overriding prefetch settings
> revert this -> boot still fails
>
> d42ced0 ARM: 8210/1: l2c: Get outer cache .write_sec callback from
> mach_desc only if not NULL
> revert this -> boot still fails
>
> 46b9af8 ARM: 8209/1: l2c: Add interface to ask hypervisor to configure L2C
> revert this -> boot still fails
>
> c94e325 ARM: 8208/1: l2c: Refactor the driver to use commit-like
> revert this -> boot passed (first bad commit).
>
>
+ linux-samsung soc and updated Thomaz's mail ID (gmail now).
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-12-05 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 16:10 regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like) Nishanth Menon
2014-12-05 16:13 ` Nishanth Menon [this message]
2014-12-05 16:23 ` Russell King - ARM Linux
2014-12-08 11:54 ` Tomasz Figa
2014-12-08 12:22 ` Russell King - ARM Linux
2014-12-08 13:54 ` Nishanth Menon
2014-12-08 15:11 ` Russell King - ARM Linux
2014-12-09 16:57 ` Nishanth Menon
2014-12-10 9:42 ` Marek Szyprowski
2014-12-11 9:29 ` Russell King - ARM Linux
2014-12-11 10:42 ` Marek Szyprowski
2014-12-22 17:04 ` Russell King - ARM Linux
2014-12-22 17:08 ` Tony Lindgren
2014-12-22 17:12 ` Nishanth Menon
2014-12-22 17:28 ` Russell King - ARM Linux
2014-12-23 11:00 ` Marek Szyprowski
2014-12-23 11:10 ` Russell King - ARM Linux
2014-12-23 16:05 ` Nishanth Menon
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=5481D9BF.2090007@ti.com \
--to=nm@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tomasz.figa@gmail.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).