From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: meson8b: add reserved memory zone to fix silent freezes
Date: Fri, 06 Oct 2017 15:59:40 -0700 [thread overview]
Message-ID: <7h1smf992b.fsf@baylibre.com> (raw)
In-Reply-To: <20171002155903.19511-1-linus.luessing@c0d3.blue> ("Linus Lüssing"'s message of "Mon, 2 Oct 2017 17:59:03 +0200")
Linus L?ssing <linus.luessing@c0d3.blue> writes:
> So far, the stress-ng tool for instance quickly resulted in a silent
> freeze of the system with no prior notice on a serial console when
> running its filesystem or memory stressor classes.
>
> Even with a panic-on-OOM and reboot-on-panic (vm.panic_on_oom=1,
> kernel.panic=10) configured, the system would neither reboot nor
> would the OOM killer get any chance to otherwise do its job.
>
> The Amlogic reference source code uses a 2MB PHYS_OFFSET. With these 2MB
> reserved via DT, stress-ng was able to run on an Odroid C1+ just fine for
> several hours, the OOM killer was able to kill processes again and if
> configured would successfully trigger a reboot of the system.
>
> Fixes: 4a69fcd3a108 ("ARM: meson: Add DTS for Odroid-C1 and Tronfy MXQ boards")
> Signed-off-by: Linus L?ssing <linus.luessing@c0d3.blue>
Applied to v4.15/dt with Martin's Tested-by,
Thanks,
Kevin
prev parent reply other threads:[~2017-10-06 22:59 UTC|newest]
Thread overview: 4+ 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 18:39 ` Martin Blumenstingl
[not found] ` <20171002234755.GA18646@ingrassia.epigenesys.com>
[not found] ` <20171003072703.GY6726@otheros>
[not found] ` <20171003082310.GA15501@ingrassia.epigenesys.com>
[not found] ` <20171003105427.GZ6726@otheros>
[not found] ` <20171004201645.GA23053@ingrassia.epigenesys.com>
[not found] ` <20171023074721.GB2049@otheros>
2017-10-28 20:27 ` Linus Lüssing
2017-10-06 22:59 ` Kevin Hilman [this message]
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=7h1smf992b.fsf@baylibre.com \
--to=khilman@baylibre.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).