From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: Versatile Express randomly fails to boot - Versatile Express to be removed from nightly testing
Date: Wed, 15 Jun 2016 10:27:50 +0100 [thread overview]
Message-ID: <57611F96.90003@arm.com> (raw)
In-Reply-To: <20160614164944.GC1041@n2100.armlinux.org.uk>
On 14/06/16 17:49, Russell King - ARM Linux wrote:
> On Tue, Jun 14, 2016 at 05:44:26PM +0100, Sudeep Holla wrote:
>> Even with higher latency if the platform is unusable, I agree to remove.
>> If you think it's usable with the updated latency(<2 2 1>) then we can
>> update it.
>
> The kernels I'm booting have that updated latency. It used to improve
> things, but for most of this year, it fails most boot attempts. Out
> of the last 21 boot attempts, all 21 attempts failed with the above
> latency value.
>
Thanks, I do see that, it's unreliable with higher latencies too. If I
increase them, it seem to work, but again as the size of the image
increases the behavior changes.
So, apart from increasing the latency or removing the DT completely, I
was thinking of 3rd option of disabling L2CC on Vexpress CA9 coretile.
Let me know if that's acceptable. I thought it's reasonable as we
still can the platform support without L2CC enabled.
Regards,
Sudeep
-->8
diff --git i/arch/arm/boot/dts/vexpress-v2p-ca9.dts
w/arch/arm/boot/dts/vexpress-v2p-ca9.dts
index b608a03ee02f..9742448b4e85 100644
--- i/arch/arm/boot/dts/vexpress-v2p-ca9.dts
+++ w/arch/arm/boot/dts/vexpress-v2p-ca9.dts
@@ -174,6 +174,7 @@
cache-level = <2>;
arm,data-latency = <1 1 1>;
arm,tag-latency = <1 1 1>;
+ status = "disabled";
};
pmu {
diff --git i/arch/arm/mm/cache-l2x0.c w/arch/arm/mm/cache-l2x0.c
index c61996c256cc..569fb1f0994b 100644
--- i/arch/arm/mm/cache-l2x0.c
+++ w/arch/arm/mm/cache-l2x0.c
@@ -1750,6 +1750,9 @@ int __init l2x0_of_init(u32 aux_val, u32 aux_mask)
if (!np)
return -ENODEV;
+ if (!of_device_is_available(np))
+ return -ENODEV;
+
if (of_address_to_resource(np, 0, &res))
return -ENODEV;
next prev parent reply other threads:[~2016-06-15 9:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 21:33 Versatile Express randomly fails to boot Russell King - ARM Linux
2015-03-16 0:04 ` Russell King - ARM Linux
2015-03-16 0:42 ` Russell King - ARM Linux
2015-03-16 9:35 ` Russell King - ARM Linux
2015-03-16 13:04 ` Versatile Express randomly fails to boot - Versatile Express to be removed from nightly testing Russell King - ARM Linux
2015-03-16 17:47 ` Sudeep Holla
2015-03-16 18:16 ` Russell King - ARM Linux
2015-03-16 19:16 ` Sudeep Holla
2015-03-16 19:52 ` Russell King - ARM Linux
2015-03-17 12:05 ` Sudeep Holla
2015-03-17 15:36 ` Russell King - ARM Linux
2015-03-17 15:51 ` Sudeep Holla
2015-03-17 16:17 ` Russell King - ARM Linux
2015-03-30 14:03 ` Russell King - ARM Linux
2015-03-30 14:48 ` Sudeep Holla
2015-03-30 15:05 ` Russell King - ARM Linux
2015-03-30 15:39 ` Sudeep Holla
2015-03-31 17:27 ` Sudeep Holla
2015-04-02 14:13 ` Russell King - ARM Linux
2015-04-02 17:38 ` Sudeep Holla
2016-06-14 15:31 ` Jon Medhurst (Tixy)
2016-06-14 15:52 ` Russell King - ARM Linux
2016-06-14 16:44 ` Sudeep Holla
2016-06-14 16:49 ` Russell King - ARM Linux
2016-06-15 9:27 ` Jon Medhurst (Tixy)
2016-06-15 9:32 ` Sudeep Holla
2016-06-15 9:50 ` Jon Medhurst (Tixy)
2016-06-15 9:59 ` Sudeep Holla
2016-06-15 9:27 ` Sudeep Holla [this message]
2016-06-14 16:31 ` Sudeep Holla
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=57611F96.90003@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).