All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: c4pt4inkrunch@gmail.com
Cc: xen-devel@lists.xensource.com
Subject: Re: trying to get vt-d working with xen 4.0.0 stable + 2.6.32.10 pvops kernel with .config file from the
Date: Tue, 4 May 2010 10:49:10 -0400	[thread overview]
Message-ID: <20100504144910.GB15544@phenom.dumpdata.com> (raw)
In-Reply-To: <0016e64765d2184ed30485011daf@google.com>

On Sat, Apr 24, 2010 at 08:08:56PM +0000, c4pt4inkrunch@gmail.com wrote:
> here is my xm dmesg i was wondering if anyone knew about these DMAR  

.. snip..
> (XEN) [VT-D]iommu.c:1078: drhd->address = fe71a000 iommu->reg = fff17000
> (XEN) [VT-D]iommu.c:1080: cap = ffffffffffffffff ecap = ffffffffffffffff
> (XEN) [VT-D]iommu.c:1086: IOMMU: unsupported

Line 1086.

1083     if ( cap_fault_reg_offset(iommu->cap) +
1084          cap_num_fault_regs(iommu->cap) * PRIMARY_FAULT_REG_LEN >=
PAGE_SIZE ||
1085          ecap_iotlb_offset(iommu->ecap) >= PAGE_SIZE )
1086     {


The iommu->cap and iommu->ecap are used. And as you can see below
the values are all 0xfffffffffffffffff which are pretty bogus.

> (XEN) ---- print_iommu_regs ----
> (XEN) drhd->address = fe71a000
> (XEN) VER = ffffffff
> (XEN) CAP = ffffffffffffffff
> (XEN) n_fault_reg = 100
> (XEN) fault_recording_offset = 3ff0
> (XEN) ECAP = ffffffffffffffff
> (XEN) GCMD = ffffffff
> (XEN) GSTS = ffffffff
> (XEN) RTADDR = ffffffffffffffff
> (XEN) CCMD = ffffffffffffffff
> (XEN) FSTS = ffffffff
> (XEN) FECTL = ffffffff
> (XEN) FEDATA = ffffffff
> (XEN) FEADDR = ffffffff
> (XEN) FEUADDR = ffffffff
> (XEN) I/O virtualisation disabled
> (XEN) Total of 8 processors activated.

Looks to me that your hardware isn't working right.

So to fix this, please follow this link:

"Intel developers also want to know about broken IOMMU/VT-d BIOS
implementations, see this email:
+http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00841.html,
so let them know all the details about your hardware and
+software if you have broken BIOS. "

      reply	other threads:[~2010-05-04 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 20:08 trying to get vt-d working with xen 4.0.0 stable + 2.6.32.10 pvops kernel with .config file from the c4pt4inkrunch
2010-05-04 14:49 ` 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=20100504144910.GB15544@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=c4pt4inkrunch@gmail.com \
    --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 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.