From: Jacob Pan <jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Jerry Snitselaar <jsnitsel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: source-id verification failures
Date: Fri, 5 Oct 2018 11:43:38 -0700 [thread overview]
Message-ID: <20181005114338.234e39ee@jacob-builder> (raw)
In-Reply-To: <20181004205724.4kqntecb6m7gcgu6@cantor>
On Thu, 4 Oct 2018 13:57:24 -0700
Jerry Snitselaar <jsnitsel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> >
> >On Tue, Oct 02, 2018 at 10:25:29AM -0700, Jerry Snitselaar wrote:
> >> I've been trying to track down a problem where an hp dl380 gen8
> >> with a Cavium QLogic BR-1860 Fabric Adapter is getting source-id
> >> verification failures when running dhclient against that
> >> interface. This started showing up when I backported the iova
> >> deferred flushing patches. So far this has only been seen on this
> >> one system, but I'm trying to understand why it appears with the
> >> new deferred flushing code. I also see it with both 4.18.10, and
> >> 4.19.0-rc6 kernels.
> >>
Hi Jerry,
Could you confirm that you see this failure in v4.19-rc6 kernel only
without "strict" mode? I don't see a connection between deferred
flushing and IR here, AFAIK deferred flush only affects DMA remapping.
Also, does the SID failure occur on other devices under the same IOMMU?
Thanks,
Jacob
next prev parent reply other threads:[~2018-10-05 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 17:25 source-id verification failures Jerry Snitselaar
2018-10-04 9:07 ` Joerg Roedel
[not found] ` <20181004090753.GC3630-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-10-04 20:57 ` Jerry Snitselaar
2018-10-04 22:07 ` Jacob Pan
2018-10-05 23:54 ` Raj, Ashok
[not found] ` <20181005235428.GB19502-7RUrO8UaCDyr4tA6zuQqW9h3ngVCH38I@public.gmane.org>
2018-10-08 16:25 ` Jerry Snitselaar
2018-10-05 18:43 ` Jacob Pan [this message]
2018-10-11 19:09 ` Jerry Snitselaar
2018-10-15 18:15 ` Jacob Pan
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=20181005114338.234e39ee@jacob-builder \
--to=jacob.jun.pan-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jsnitsel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.