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: Mon, 30 Mar 2015 15:48:08 +0100 [thread overview]
Message-ID: <55196228.5050805@arm.com> (raw)
In-Reply-To: <20150330140333.GJ24899@n2100.arm.linux.org.uk>
Hi Russell,
On 30/03/15 15:03, Russell King - ARM Linux wrote:
> On Tue, Mar 17, 2015 at 04:17:48PM +0000, Russell King - ARM Linux wrote:
>> On Tue, Mar 17, 2015 at 03:51:53PM +0000, Sudeep Holla wrote:
>>> That's bad. I started with 2 cycles for all(rd/wr/setup) latencies(data
>>> and tag ram) and narrowed down to this setting with multiple
>>> experiments. I did try booting 10 times each time at-least.
>>>
>>> Since the bootmon sets 8 cycles for all the latencies, does it make
>>> sense to try that setting to check if the issue you are seeing is
>>> related to L2 latencies at all. Meanwhile I will continue my testing.
>>
>> For me <2 2 1> works - so read and write latencies of 2, setup of 1.
>
> So what's happening? Is someone going to update the dtb to adjust the
> latencies so that we can have a reliable platform?
>
Though <2 2 1> works fine most of the time, I did try testing continuous
reboot overnight and it failed. I kept increasing the latencies and
found out that even max latency of <8 8 8> could not survive continuous
overnight reboot test and it fails with exact same issue.
So I am not sure if we can consider it as a fix. However if we are OK to
have *mostly reliable*, then we can push that change.
Regards,
Sudeep
next prev parent reply other threads:[~2015-03-30 14:48 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 [this message]
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
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=55196228.5050805@arm.com \
--to=sudeep.holla@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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