Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
To: Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	"Williams,
	Mitch A"
	<mitch.a.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	jesse.brandeburg-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Subject: Re: [BUG 4.1-rc4] i40e VF creation breaks vt-d
Date: Fri, 22 May 2015 12:09:26 +0200	[thread overview]
Message-ID: <20150522100926.GA1928@suse.de> (raw)
In-Reply-To: <555DC288.5030108-l3A5Bk7waGM@public.gmane.org>

Hey Alex,

On Thu, May 21, 2015 at 01:33:28PM +0200, Alexander Graf wrote:
> While trying to get a sense for performance of i40e and i40evf, I
> figured I'd try and create a VF device on the host and activate it.
> However, as soon as I brought the VF up, my host became unreachable. The
> kernel is current 4.1-rc4.
> 
> Main network is connected through ixgbe (eth1), i40e is on a
> direct-connect connection with another system. The host is an Intel
> Haswell box with XAPIC and Vt-d enabled.

It is weird that you see DMAR faults two days after you tried this. Are
there any messages from the IOMMU around the time you enabled the VF?

Does it work with iommu disabled?

> ---- almost 2 days pass ----
> 
> [    9.061798] dmar: DRHD: handling fault status reg 2
> [    9.072566] dmar: INTR-REMAP: Request device [[03:00.0] fault index 5e
> [    9.072566] INTR-REMAP:[fault reason 34] Present field in the IRTE
> entry is clear

The timing info is indeed weird and might indicate another problem
outside of the iommu space. The DMAR faults might just be a follow-on
error then.


	Joerg

      parent reply	other threads:[~2015-05-22 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 11:33 [BUG 4.1-rc4] i40e VF creation breaks vt-d Alexander Graf
     [not found] ` <555DC288.5030108-l3A5Bk7waGM@public.gmane.org>
2015-05-22 10:09   ` Joerg Roedel [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=20150522100926.GA1928@suse.de \
    --to=jroedel-l3a5bk7wagm@public.gmane.org \
    --cc=agraf-l3A5Bk7waGM@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jesse.brandeburg-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=mitch.a.williams-ral2JQCrhuEAvxtiuMwx3w@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