From: Jean Guyader <jean.guyader@eu.citrix.com>
To: Neo Jia <neojia@gmail.com>
Cc: xen-devel@lists.xensource.com, "Han, Weidong" <weidong.han@intel.com>
Subject: Re: VT-d warnings on Intel DQ35JO
Date: Thu, 05 Jun 2008 08:34:49 +0100 [thread overview]
Message-ID: <48479719.4070800@eu.citrix.com> (raw)
In-Reply-To: <5d649bdb0806050030j5bf6ad6fhb8416cf568061d4e@mail.gmail.com>
Neo Jia wrote:
> hi,
>
> This is what I get on the Intel DQ35JO. Is it critical?
>
> (XEN) Brought up 2 CPUs
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests disabled
> (XEN) [VT-D]iommu.c:764: iommu_page_fault: iommu->reg = ffff828bfff57000
> (XEN) [VT-D]iommu.c:733: iommu_fault_status: Fault Overflow
> (XEN) [VT-D]iommu.c:720: iommu_fault:DMA Write: 0:2.0 addr f00000000
> REASON 5 iommu->reg = ffff828bfff57000
> (XEN) print_vtd_entries: iommu = ffff83007aefb480 bdf = 0:2:0 gmfn = f00000
> (XEN) root_entry = ffff83007c06e000
> (XEN) root_entry[0] = 7c18b001
> (XEN) context = ffff83007c18b000
> (XEN) context[10] = 101_7d1dc001
> (XEN) l3 = ffff83007d1dc000
> (XEN) l3_index = 3c
> (XEN) l3[3c] = 0
> (XEN) l3[3c] not present
> (XEN) *** LOADING DOMAIN 0 ***
>
I had almost the same error with this same motherboard, you should
upgrade your bios.
--
Jean Guyader
prev parent reply other threads:[~2008-06-05 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 7:30 VT-d warnings on Intel DQ35JO Neo Jia
2008-06-05 7:34 ` Jean Guyader [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=48479719.4070800@eu.citrix.com \
--to=jean.guyader@eu.citrix.com \
--cc=neojia@gmail.com \
--cc=weidong.han@intel.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.