[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYvKHDqghKAWy_8MP6+hTXmQqaoTT_STT7v74Oh+G6hKFQ@mail.gmail.com>
Date: Thu, 14 Jul 2022 17:05:53 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Christoph Hellwig <hch@....de>,
Anshuman Khandual <anshuman.khandual@....com>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
Tom Lendacky <thomas.lendacky@....com>, conor@...nel.org,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>
Subject: Re: [next] Kernel panic - not syncing: swiotlb_init_remap: nslabs = 0
too small
Hi Christoph and Anshuman,
On Thu, 14 Jul 2022 at 13:52, Christoph Hellwig <hch@....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
Powered by blists - more mailing lists