From: Breno Leitao <leitao@debian.org>
To: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
catalin.marinas@arm.com, mark.rutland@arm.com
Cc: puranjay@kernel.org, linux-arm-kernel@lists.infradead.org,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
rmikey@meta.com, kernel-team@meta.com
Subject: Re: [PATCH 0/2] iommu/arm-smmu-v3: SMMU hitting kdump mid-air
Date: Fri, 11 Sep 2026 07:57:49 -0700 [thread overview]
Message-ID: <aqQWrz74_sOmyZrT@gmail.com> (raw)
In-Reply-To: <20260911-smmu_fix_aws-v1-0-75870bf9655b@debian.org>
On Fri, Sep 11, 2026 at 07:54:43AM -0700, Breno Leitao wrote:
> I've found that kdump does not work on some ARM host, such as AWS
> Graviton metal, and the SMMU is what seems to kills it.
>
> The capture kernel dies about a second after it resets the SMMU, part
> way through PCI enumeration, and takes the machine with it.
>
> There is no panic and no oops: the console stops mid-line and the box
> reboots, leaving no vmcore, no log and nothing on disk. Crashes on this
> hardware mostly produce no dump at all.
>
> This is my theory, from an "outsider view":
This should really have been tagged RFC — apologies for missing that.
next prev parent reply other threads:[~2026-09-11 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 14:54 Breno Leitao
2026-09-11 14:54 ` [PATCH 1/2] iommu/arm-smmu-v3: inherit the previous kernel's stream table in kdump Breno Leitao
2026-09-11 14:54 ` [PATCH 2/2] iommu/arm-smmu-v3: defer attach in kdump so inherited entries survive probe Breno Leitao
2026-09-11 14:57 ` Breno Leitao [this message]
2026-09-11 22:31 ` [PATCH 0/2] iommu/arm-smmu-v3: SMMU hitting kdump mid-air Nicolin Chen
2026-09-14 10:39 ` Breno Leitao
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=aqQWrz74_sOmyZrT@gmail.com \
--to=leitao@debian.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel-team@meta.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=puranjay@kernel.org \
--cc=rmikey@meta.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®