From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@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: Thu, 4 Oct 2018 11:07:53 +0200 [thread overview]
Message-ID: <20181004090753.GC3630@8bytes.org> (raw)
In-Reply-To: <20181002172529.fjapu46h5y57m3f7@cantor>
Hi Jerry,
thanks for the report.
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.
>
> [35645.282021] bna 0000:24:00.1 ens5f1: link down
> [35645.298396] bna 0000:24:00.0 ens5f0: link down
> [35650.313210] DMAR: DRHD: handling fault status reg 2
> [35650.332477] DMAR: [INTR-REMAP] Request device [24:00.0] fault index 14 [fault reason 38] Blocked an interrupt request due to source-id verification failure
> [35655.137667] bna 0000:24:00.0 ens5f0: link up
> [35657.532454] bna 0000:24:00.1 ens5f1: link up
> [35664.281563] bna 0000:24:00.1 ens5f1: link down
> [35664.298103] bna 0000:24:00.0 ens5f0: link down
> [35669.313568] DMAR: DRHD: handling fault status reg 102
> [35669.333198] DMAR: [INTR-REMAP] Request device [24:00.0] fault index 14 [fault reason 38] Blocked an interrupt request due to source-id verification failure
> [35674.081212] bna 0000:24:00.0 ens5f0: link up
> [35674.981280] bna 0000:24:00.1 ens5f1: link up
>
>
> Any ideas?
No, not yet. Can you please post the output of lscpi -vvv?
Jacob, can you or someone from your team please also have a look into
this problem report?
Thanks,
Joerg
next prev parent reply other threads:[~2018-10-04 9:07 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 [this message]
[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
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=20181004090753.GC3630@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox