mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Birk Skyum <birk.skyum@pm.me>
To: Val Packett <val@packett.cool>
Cc: Stephan Gerhold <stephan.gerhold@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Xin Liu <xin.liu@oss.qualcomm.com>,
	Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
	Nikita Travkin <nikita@trvn.ru>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: hamoa: Add remoteproc in EL2 device trees
Date: Mon, 14 Sep 2026 14:37:53 +0000	[thread overview]
Message-ID: <20260914143445.yoga-kvm-regression-test-birk@pm.me> (raw)

Hi,

I reproduced this failure on a Lenovo Yoga Slim 7x (83ED), BIOS NHCN62WW,
using Arch Linux ARM kernel 7.2.4-1 and SLBounce. Boot stalled with repeated
SMMU faults, including FSR=0x402, SID=0x1000 and IOVA=0x86b020c0.

I then tested Jens Glathe's non-PAS EL2 overlay [1]. Keeping the kernel,
initramfs, boot arguments and SLBounce unchanged, removing the two
top-level ADSP/CDSP iommus properties allowed Linux to reach userspace and
initialize KVM.

Subsequent one- and two-vCPU Linux guests passed CPU and timer checks and
shut down cleanly across two cold boots. The host remained responsive, and
post-test kernel-log searches found no "Unhandled context fault" messages.

These were RAM-only tests, without GPU or remoteproc modules, so they
validate boot and basic KVM operation rather than full desktop or DSP
support.

[1] https://github.com/jglathe/linux_ms_dev_kit/commit/ce20a20db795f299983f092fb899e0ad1c005be3

Thanks,
Birk


             reply	other threads:[~2026-09-14 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 14:37 Birk Skyum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-02  5:54 Xin Liu
2026-02-02 15:28 ` Abel Vesa
2026-03-04 20:16 ` Bjorn Andersson
2026-03-05 10:57   ` Stephan Gerhold
2026-03-28  8:22     ` Val Packett

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=20260914143445.yoga-kvm-regression-test-birk@pm.me \
    --to=birk.skyum@pm.me \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jens.glathe@oldschoolsolutions.biz \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita@trvn.ru \
    --cc=stephan.gerhold@linaro.org \
    --cc=val@packett.cool \
    --cc=xin.liu@oss.qualcomm.com \
    /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
all inboxes | Powered by JetHome®