From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: VT-d faults with Integrated Intel graphics on 4.6
Date: Tue, 25 Aug 2015 14:55:31 +0800 [thread overview]
Message-ID: <55DC1163.7050005@intel.com> (raw)
In-Reply-To: <CABfawhnDioJNTMyfKOkhz8daQY=DJr6G-DyvMyhKPS_mLEdaTQ@mail.gmail.com>
On 8/25/2015 8:19 AM, Tamas K Lengyel wrote:
> Hi everyone,
> I saw some people passingly mention this on the list before but just in
> case it has been missed, my serial is also being spammed with the following
> printouts with both Xen 4.6 RC1 and the latest staging build:
>
> ...
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr
> 33487d7000, iommu reg = ffff82c000201000
> (XEN) [VT-D]DMAR: reason 06 - PTE Read access is not set
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr
> 33487d7000, iommu reg = ffff82c000201000
> (XEN) [VT-D]DMAR: reason 06 - PTE Read access is not set
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr
> 33487d7000, iommu reg = ffff82c000201000
> (XEN) [VT-D]DMAR: reason 06 - PTE Read access is not set
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr
> 33487d7000, iommu reg = ffff82c000201000
> (XEN) [VT-D]DMAR: reason 06 - PTE Read access is not set
> (XEN) [VT-D]DMAR:[DMA Read] Request device [0000:00:02.0] fault addr
> 2610742000, iommu reg = ffff82c000201000
> (XEN) [VT-D]DMAR: reason 07 - Next page table ptr is invalid
> ...
>
What's your platform? BDW? And how much memory is set to your guest OS?
Just at first glance to fault address, this seems be issued from some
known erratas on BDS and SKL.
Thanks
Tiejun
> The device in question is an integrated Intel graphics card:
>
> 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
> Processor Family Integrated Graphics Controller (rev 09)
>
> The only way I found to stop the messages from making my serial connection
> useless was by assigning the device to xen-pciback.
>
> Cheers,
> Tamas
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2015-08-25 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 0:19 VT-d faults with Integrated Intel graphics on 4.6 Tamas K Lengyel
2015-08-25 6:55 ` Chen, Tiejun [this message]
2015-08-25 14:43 ` Konrad Rzeszutek Wilk
2015-08-25 15:29 ` Tamas K Lengyel
2015-08-26 16:19 ` Malcolm Crossley
2015-08-26 17:15 ` Konrad Rzeszutek Wilk
2015-08-26 17:20 ` Andrew Cooper
2015-08-26 17:28 ` Konrad Rzeszutek Wilk
2015-08-26 17:40 ` Andrew Cooper
2015-08-27 3:12 ` Chen, Tiejun
2015-08-27 3:06 ` Chen, Tiejun
2015-08-27 11:03 ` Konrad Rzeszutek Wilk
2015-08-28 2:05 ` Chen, Tiejun
2015-08-28 16:51 ` Konrad Rzeszutek Wilk
2015-12-01 16:16 ` Konrad Rzeszutek Wilk
2015-12-02 0:59 ` Wu, Feng
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=55DC1163.7050005@intel.com \
--to=tiejun.chen@intel.com \
--cc=tamas.k.lengyel@gmail.com \
--cc=xen-devel@lists.xen.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 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.