From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: iommu@lists.linux-foundation.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] "iommu/amd: Relax locking in dma_ops path" makes tg3 ethernet transmit queue timeout
Date: Fri, 21 Aug 2020 21:50:33 +0800 [thread overview]
Message-ID: <5D7A63DF-D360-4453-845C-924F4C13E3DB@canonical.com> (raw)
In-Reply-To: <20200821134300.GM3354@suse.de>
Hi Joerg,
> On Aug 21, 2020, at 21:43, Joerg Roedel <jroedel@suse.de> wrote:
>
> Hi Kai,
>
> On Mon, Jun 29, 2020 at 08:33:22PM +0800, Kai-Heng Feng wrote:
>> I am still seeing the issue on v5.8-rc3. The issue goes away as soon
>> as "iommu=off" is added.
>
> Can you probably help with debugging this issue? I've had no luck so far
> getting my hands on a machine with tg3 hardware and an AMD IOMMU.
Of course, I still have the system at my side.
The offending commit is 92d420ec028d ("iommu/amd: Relax locking in dma_ops path"), however be62dbf554c5 ("iommu/amd: Convert AMD iommu driver to the dma-iommu api") removed .map_page entirely so I don't know where to start.
Kai-Heng
>
> Regards,
>
> Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-08-21 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 9:06 [Regression] "iommu/amd: Relax locking in dma_ops path" makes tg3 ethernet transmit queue timeout Kai-Heng Feng
2020-05-18 13:32 ` Joerg Roedel
2020-05-18 14:05 ` Kai-Heng Feng
2020-05-18 15:32 ` Kai-Heng Feng
2020-06-29 12:33 ` Kai-Heng Feng
2020-08-21 13:43 ` Joerg Roedel
2020-08-21 13:50 ` Kai-Heng Feng [this message]
2020-08-21 14:43 ` Joerg Roedel
2020-08-23 13:19 ` Kai-Heng Feng
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=5D7A63DF-D360-4453-845C-924F4C13E3DB@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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).