From: Conor Dooley <conor@kernel.org>
To: hch@lst.de
Cc: Tianyu.Lan@microsoft.com, iommu@lists.linux.dev,
linux-doc@vger.kernel.org, lkp@intel.com, lkp@lists.01.org,
ltykernel@gmail.com, oliver.sang@intel.com
Subject: Re: [EXTERNAL] [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small
Date: Wed, 13 Jul 2022 17:11:34 +0100 [thread overview]
Message-ID: <20220713161133.1707380-1-conor@kernel.org> (raw)
In-Reply-To: <20220713060246.GA13497@lst.de>
FWIW, I hit this on a PolarFire SoC.
Was relieved to see that it was not another wacky edge case like my
last run-in with swiotlb issues! If you could CC me on the fix that'd
be great.
Thanks,
Conor.
prev parent reply other threads:[~2022-07-13 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Ys43FtIumAsHPn+y@xsang-OptiPlex-9020>
2022-07-13 5:58 ` [EXTERNAL] [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small Tianyu Lan
2022-07-13 6:02 ` Christoph Hellwig
2022-07-13 16:11 ` Conor Dooley [this message]
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=20220713161133.1707380-1-conor@kernel.org \
--to=conor@kernel.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ltykernel@gmail.com \
--cc=oliver.sang@intel.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;
as well as URLs for NNTP newsgroup(s).