xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [pvops-2.6.31.12 ]Fatal DMA error! Please use 'swiotlb=force' kernel BUG at drivers/pci/xen-iommu.c:227! invalid opcode: 0000 [#1] SMP
Date: Mon, 22 Mar 2010 15:10:55 -0400	[thread overview]
Message-ID: <20100322191055.GA31521@phenom.dumpdata.com> (raw)
In-Reply-To: <1954256379.20100311114453@eikelenboom.it>

On Thu, Mar 11, 2010 at 11:44:53AM +0100, Sander Eikelenboom wrote:
> Hi Konrad ,
> 
> On this machine i'm using
> - xen-3.4.2
> - pvops 2.6.31.6 dom0 kernel
> - debian stock 2.6.26.2-xen kernels
> - All are 64bit, total system mem is 8GB, no hardware iommu present.
> 
> I'm passing through several pci devices with great succes (worked stable for several months)
> - Soundcard
> - 1 PCI and 1 PCI-e USB 2.0 cards used for videograbbing
> 
> 
> 
> Now i have tried to passthrough a third USB card, (PCI-e, USB 3.0 in this case), with a new pvops 2.6.31.12 kernel.
> 
> But although i specified swiotlb=force, something seems to go wrong with DMA mapping, dmesg from the domU shows the error below.
> The complete dmesg output is attached.

Ugh. There is one more parameter you need to add, that is 'iommu=soft'.

That 'use swiotlb=force' nees to be fixed. Thanks for spotting it.

      parent reply	other threads:[~2010-03-22 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 10:44 [pvops-2.6.31.12 ]Fatal DMA error! Please use 'swiotlb=force' kernel BUG at drivers/pci/xen-iommu.c:227! invalid opcode: 0000 [#1] SMP Sander Eikelenboom
2010-03-11 20:35 ` Konrad Rzeszutek Wilk
2010-03-22 19:10 ` Konrad Rzeszutek Wilk [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=20100322191055.GA31521@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xensource.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).