From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: sachinp@linux.vnet.ibm.com,
Linux kernel regressions list <regressions@lists.linux.dev>,
Gaurav Batra <gbatra@linux.vnet.ibm.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
linux-kernel@vger.kernel.org,
Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
"Linux regression tracking \(Thorsten Leemhuis\)"
<regressions@leemhuis.info>, Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Probing nvme disks fails on Upstream kernels on powerpc Maxconfig
Date: Mon, 22 May 2023 16:38:18 +0530 [thread overview]
Message-ID: <20230522110818.GB3902@linux.vnet.ibm.com> (raw)
In-Reply-To: <87edn8ak4d.fsf@mail.lhotse>
* Michael Ellerman <mpe@ellerman.id.au> [2023-05-22 17:41:22]:
> Srikar Dronamraju <srikar@linux.vnet.ibm.com> writes:
> > * Alexey Kardashevskiy <aik@ozlabs.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
prev parent reply other threads:[~2023-05-22 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 9:53 Probing nvme disks fails on Upstream kernels on powerpc Maxconfig Srikar Dronamraju
2023-04-04 13:49 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-05 5:45 ` Michael Ellerman
2023-04-13 12:09 ` Alexey Kardashevskiy
2023-05-22 7:24 ` Srikar Dronamraju
2023-05-22 7:41 ` Michael Ellerman
2023-05-22 11:08 ` Srikar Dronamraju [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=20230522110818.GB3902@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=gbatra@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sachinp@linux.vnet.ibm.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).