[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230522110818.GB3902@linux.vnet.ibm.com>
Date: Mon, 22 May 2023 16:38:18 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Alexey Kardashevskiy <aik@...abs.ru>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>, Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
sachinp@...ux.vnet.ibm.com,
Abdul Haleem <abdhalee@...ux.vnet.ibm.com>,
Gaurav Batra <gbatra@...ux.vnet.ibm.com>,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: Probing nvme disks fails on Upstream kernels on powerpc Maxconfig
* Michael Ellerman <mpe@...erman.id.au> [2023-05-22 17:41:22]:
> Srikar Dronamraju <srikar@...ux.vnet.ibm.com> writes:
> > * Alexey Kardashevskiy <aik@...abs.ru> [2023-04-13 22:09:22]:
> >
> >> > > On 23.03.23 10:53, Srikar Dronamraju wrote:
> >> > > >
> > Hi Alexey, Michael
> >
> > Sorry for the late reply, but I didnt have access to this large system.
> > This weekend, I did get access and tested with the patch. However it didn't
> > help much, system is still stuck at dracut with similar message except the
> > trace.
> >
> > However this patch
> > https://lore.kernel.org/all/20230418204401.13168-1-gbatra@linux.vnet.ibm.com/
> > from Gaurav Batra does solve this issue.
>
> Thanks.
>
> There was a v3 of that patch:
> https://lore.kernel.org/all/20230504175913.83844-1-gbatra@linux.vnet.ibm.com/
>
> Which is merged now into mainline as:
> 096339ab84f3 ("powerpc/iommu: DMA address offset is incorrectly calculated with 2MB TCEs")
>
> Presumably it also fixes the bug for you, so I'll mark this as fixed,
> but if you can test that exact commit that would be good to confirm the
> bug is fixed in mainline.
>
Yes verified with mainline kernel and also with the v3.
This patch/commit does fix it.
--
Thanks and Regards
Srikar Dronamraju
Powered by blists - more mailing lists