From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH] ARM: dts: meson8b: add reserved memory zone to fix silent freezes Date: Fri, 06 Oct 2017 15:59:40 -0700 Message-ID: <7h1smf992b.fsf@baylibre.com> References: <20171002155903.19511-1-linus.luessing@c0d3.blue> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20171002155903.19511-1-linus.luessing@c0d3.blue> ("Linus =?utf-8?Q?L=C3=BCssing=22's?= message of "Mon, 2 Oct 2017 17:59:03 +0200") Sender: linux-kernel-owner@vger.kernel.org To: Linus =?utf-8?Q?L=C3=BCssing?= Cc: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Carlo Caione , Martin Blumenstingl , Mark Rutland , Rob Herring , Russell King List-Id: devicetree@vger.kernel.org Linus L=C3=BCssing 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=3D1, > kernel.panic=3D10) 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 bo= ards") > Signed-off-by: Linus L=C3=BCssing Applied to v4.15/dt with Martin's Tested-by, Thanks, Kevin