From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Christoph Hellwig <hch@lst.de>,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
conor@kernel.org, Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [next] Kernel panic - not syncing: swiotlb_init_remap: nslabs = 0 too small
Date: Thu, 14 Jul 2022 17:05:53 +0530 [thread overview]
Message-ID: <CA+G9fYvKHDqghKAWy_8MP6+hTXmQqaoTT_STT7v74Oh+G6hKFQ@mail.gmail.com> (raw)
In-Reply-To: <20220714082212.GA30886@lst.de>
Hi Christoph and Anshuman,
On Thu, 14 Jul 2022 at 13:52, Christoph Hellwig <hch@lst.de> wrote:
>
> On Thu, Jul 14, 2022 at 01:50:02PM +0530, Anshuman Khandual wrote:
> > 26ffb91fa5e0fb282e8 ("swiotlb: split up the global swiotlb lock")
>
> This has been replace with 20347fca71a387a3751f7bb270062616ddc5317a
> that should fix the issue.
Thanks for your inputs.
As per your suggestion, I have reverted those two patches on Linux next tree
and built for arm64 and the boot test successfully.
467f49f87d84 Revert "swiotlb: split up the global swiotlb lock"
2706e93f7f8a Revert "swiotlb: fail map correctly with failed io_tlb_default_mem"
Boot pass log link,
https://lkft.validation.linaro.org/scheduler/job/5284375#L583
Best Regards
Naresh Kamboju
--
Linaro LKFT
https://lkft.linaro.org
prev parent reply other threads:[~2022-07-14 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 7:47 Naresh Kamboju
2022-07-14 8:20 ` Anshuman Khandual
2022-07-14 8:22 ` Christoph Hellwig
2022-07-14 11:35 ` Naresh Kamboju [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=CA+G9fYvKHDqghKAWy_8MP6+hTXmQqaoTT_STT7v74Oh+G6hKFQ@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=conor@kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=m.szyprowski@samsung.com \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.lendacky@amd.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