From: linus.luessing@c0d3.blue (Linus Lüssing)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM: dts: meson8b: add reserved memory zone to fix silent freezes
Date: Mon, 23 Oct 2017 09:47:21 +0200 [thread overview]
Message-ID: <20171023074721.GB2049@otheros> (raw)
In-Reply-To: <20171004201645.GA23053@ingrassia.epigenesys.com>
Hi Kevin,
Just wanted to let you know that Emiliano and I are currently
debugging further off-list.
So far I can reproduce that:
a) For the binary kernel image Emiliano sent me I can reproduce
his hang ups during boot on my Odroid C1+.
b) The 2MB reserved memory region this patch adds does not help
for this image.
c) Removing the "arm,filter-range" as proposed by Emiliano back
then instead of adding this reserved memory zone fixes my freezes
during boot in Emiliano's image and during stress-ng for my kernel
image, too.
I'm currently continuing to bisect which difference in Emiliano's
and my kernel image makes mine boot successfully but not
Emiliano's. (And I'm continuing reading and testing with the
filter-range option to better understand what it's presence - or
absence - does exactly)
If these observations ring a bell for anyone here, I'd be curious
to hear what they think.
Regards, Linus
next prev parent reply other threads:[~2017-10-23 7:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:59 [PATCH] ARM: dts: meson8b: add reserved memory zone to fix silent freezes Linus Lüssing
2017-10-02 15:59 ` Linus Lüssing
2017-10-02 15:59 ` Linus Lüssing
2017-10-02 15:59 ` Linus Lüssing
2017-10-02 18:39 ` Martin Blumenstingl
2017-10-02 18:39 ` Martin Blumenstingl
2017-10-02 18:39 ` Martin Blumenstingl
2017-10-02 18:39 ` Martin Blumenstingl
2017-10-02 23:47 ` Emiliano Ingrassia
2017-10-03 7:27 ` Linus Lüssing
2017-10-03 8:23 ` Emiliano Ingrassia
2017-10-03 10:54 ` Linus Lüssing
2017-10-04 20:16 ` Emiliano Ingrassia
2017-10-23 7:47 ` Linus Lüssing [this message]
2017-10-28 20:27 ` Linus Lüssing
2017-10-28 20:27 ` Linus Lüssing
2017-10-28 20:27 ` Linus Lüssing
2017-10-28 20:27 ` Linus Lüssing
2017-10-06 22:59 ` Kevin Hilman
2017-10-06 22:59 ` Kevin Hilman
2017-10-06 22:59 ` Kevin Hilman
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=20171023074721.GB2049@otheros \
--to=linus.luessing@c0d3.blue \
--cc=linus-amlogic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.