All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steev Klimaszewski <threeway@gmail.com>
To: jonathan@marek.ca
Cc: abel.vesa@linaro.org, andersson@kernel.org,
	christopher.obbard@linaro.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, konradybcio@kernel.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, quic_rjendra@quicinc.com,
	robh@kernel.org, sibi.sankar@oss.qualcomm.com,
	stephan.gerhold@linaro.org
Subject: Re: [PATCH] arm64: dts: qcom: x1e: bus is 40-bits (fix 64GB models)
Date: Sun, 30 Nov 2025 18:13:53 -0600	[thread overview]
Message-ID: <20251201001353.9852-1-threeway@gmail.com> (raw)
In-Reply-To: <35615ad4-5b86-577f-4695-c6cd85206334@marek.ca>

Hi All,

On my Thinkpad T14S OLED with 64GB, with this patch applied, I am unable to boot
the laptop anymore.  It doesn't matter whether I have mem=30GB, nor if I set
CONFIG_ARM64_VA_BITS_39, or not limiting the ram - shortly after loading the
device tree, the laptop just resets.  

I have tried over 20 boots with it applied, as well as trying both booting a
working kernel, and then rebooting as well as cold boots.


-- steev

  reply	other threads:[~2025-12-01  0:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 21:29 [PATCH] arm64: dts: qcom: x1e: bus is 40-bits (fix 64GB models) Jonathan Marek
2025-11-28 10:26 ` Stephan Gerhold
2025-11-28 10:52   ` Konrad Dybcio
2025-11-28 14:49     ` Jonathan Marek
2025-12-01 13:40       ` Konrad Dybcio
2025-11-28 14:39   ` Jonathan Marek
2025-11-28 16:03     ` Stephan Gerhold
2025-11-28 16:34       ` Jonathan Marek
2025-11-28 22:10         ` Christopher Obbard
2025-11-28 22:39           ` Christopher Obbard
2025-11-28 23:56           ` Jonathan Marek
2025-12-01  0:13             ` Steev Klimaszewski [this message]
2025-12-01  2:06               ` Jonathan Marek
2025-12-01  2:25                 ` Steev Klimaszewski
2026-01-16 21:39 ` Bjorn Andersson
2026-01-16 22:53   ` Jonathan Marek
2026-01-16 23:19     ` Bjorn Andersson
2026-01-16 23:45       ` Jonathan Marek

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=20251201001353.9852-1-threeway@gmail.com \
    --to=threeway@gmail.com \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=christopher.obbard@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathan@marek.ca \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_rjendra@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sibi.sankar@oss.qualcomm.com \
    --cc=stephan.gerhold@linaro.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.