[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90a74369a2c4d9453de733a46fdd0ef1@mainlining.org>
Date: Wed, 21 Jan 2026 15:21:28 +0100
From: barnabas.czeman@...nlining.org
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio
<konradybcio@...nel.org>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Gabriel Gonzales
<semfault@...root.org>, Kees Cook <kees@...nel.org>, Tony Luck
<tony.luck@...el.com>, "Guilherme G. Piccoli" <gpiccoli@...lia.com>,
Biswapriyo Nath <nathbappai@...il.com>, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org, phone-devel@...r.kernel.org,
~postmarketos/upstreaming@...ts.sr.ht, linux@...nlining.org
Subject: Re: [PATCH v2 2/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Correct
reserved memory ranges
On 2026-01-21 13:45, Konrad Dybcio wrote:
> On 1/16/26 4:54 PM, Barnabás Czémán wrote:
>> The device was crashing on high memory load because the reserved
>> memory
>> ranges was wrongly defined. Correct the ranges for avoid the crashes.
>> Change the ramoops memory range to match with the values from the
>> recovery
>> to be able to get the results from the device.
>>
>> Fixes: 9b1a6c925c88 ("arm64: dts: qcom: sm6125: Initial support for
>> xiaomi-ginkgo")
>> Signed-off-by: Barnabás Czémán <barnabas.czeman@...nlining.org>
>> ---
>
> Have you verified this new and improved(tm) map e.g. by booting up
> the kernel with memtest=1 in cmdline?
I have verified with cat /dev/zero | tail | sleep 5
I can test with memtest=1 also
>
> Konrad
Powered by blists - more mailing lists