From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jason Andryuk <jandryuk@gmail.com>,
<intel-gfx@lists.freedesktop.org>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Intel-gfx] i915 dma faults on Xen
Date: Wed, 14 Oct 2020 20:37:06 +0100 [thread overview]
Message-ID: <1a3b90f4-564e-84d3-fd6a-3454e8753579@citrix.com> (raw)
In-Reply-To: <CAKf6xpv-LRCuo-qHHWMuukYtvJiR-i+-YhLUOZeqoAFd-=swEQ@mail.gmail.com>
On 14/10/2020 20:28, Jason Andryuk wrote:
> Hi,
>
> Bug opened at https://gitlab.freedesktop.org/drm/intel/-/issues/2576
>
> I'm seeing DMA faults for the i915 graphics hardware on a Dell
> Latitude 5500. These were captured when I plugged into a Dell
> Thunderbolt dock with two DisplayPort monitors attached. Xen 4.12.4
> staging and Linux 5.4.70 (and some earlier versions).
>
> Oct 14 18:41:49.056490 kernel:[ 85.570347] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056494 kernel:[ 85.570395] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056589 VM hypervisor: (XEN) [VT-D]DMAR:[DMA Read]
> Request device [0000:00:02.0] fault addr 39b5845000, iommu reg =
> ffff82c00021d000
> Oct 14 18:41:49.056594 VM hypervisor: (XEN) [VT-D]DMAR: reason 06 -
> PTE Read access is not set
> Oct 14 18:41:49.056784 kernel:[ 85.570668] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056789 kernel:[ 85.570687] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056885 VM hypervisor: (XEN) [VT-D]DMAR:[DMA Read]
> Request device [0000:00:02.0] fault addr 4238d0a000, iommu reg =
> ffff82c00021d000
> Oct 14 18:41:49.056890 VM hypervisor: (XEN) [VT-D]DMAR: reason 06 -
> PTE Read access is not set
>
> They repeat. In the log attached to
> https://gitlab.freedesktop.org/drm/intel/-/issues/2576, they start at
> "Oct 14 18:41:49.056589" and continue until I unplug the dock around
> "Oct 14 18:41:54.801802".
>
> I've also seen similar messages when attaching the laptop's HDMI port
> to a 4k monitor. The eDP display by itself seems okay.
>
> I tried Fedora 31 & 32 live images with intel_iommu=on, so no Xen, and
> didn't see any errors
>
> This is a kernel & xen log with drm.debug=0x1e. It also includes some
> application (glass) logging when it changes resolutions which seems to
> set off the DMA faults. 5500-igfx-messages-kern-xen-glass
>
> Running xen with iommu=no-igfx disables the iommu for the i915
> graphics and no faults are reported. However, that breaks some other
> devices (Dell Latitude 7200 and 5580) giving a black screen with:
>
> Oct 10 13:24:37.022117 kernel:[ 14.884759] i915 0000:00:02.0: Failed
> to idle engines, declaring wedged!
> Oct 10 13:24:37.022118 kernel:[ 14.964794] i915 0000:00:02.0: Failed
> to initialize GPU, declaring it wedged!
>
> Any suggestions welcome.
Presumably this is with a PV dom0. What are 39b5845000 and 4238d0a000
in the machine memory map?
This smells like a missing RMRR in the ACPI tables.
~Andrew
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jason Andryuk <jandryuk@gmail.com>,
<intel-gfx@lists.freedesktop.org>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: i915 dma faults on Xen
Date: Wed, 14 Oct 2020 20:37:06 +0100 [thread overview]
Message-ID: <1a3b90f4-564e-84d3-fd6a-3454e8753579@citrix.com> (raw)
In-Reply-To: <CAKf6xpv-LRCuo-qHHWMuukYtvJiR-i+-YhLUOZeqoAFd-=swEQ@mail.gmail.com>
On 14/10/2020 20:28, Jason Andryuk wrote:
> Hi,
>
> Bug opened at https://gitlab.freedesktop.org/drm/intel/-/issues/2576
>
> I'm seeing DMA faults for the i915 graphics hardware on a Dell
> Latitude 5500. These were captured when I plugged into a Dell
> Thunderbolt dock with two DisplayPort monitors attached. Xen 4.12.4
> staging and Linux 5.4.70 (and some earlier versions).
>
> Oct 14 18:41:49.056490 kernel:[ 85.570347] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056494 kernel:[ 85.570395] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056589 VM hypervisor: (XEN) [VT-D]DMAR:[DMA Read]
> Request device [0000:00:02.0] fault addr 39b5845000, iommu reg =
> ffff82c00021d000
> Oct 14 18:41:49.056594 VM hypervisor: (XEN) [VT-D]DMAR: reason 06 -
> PTE Read access is not set
> Oct 14 18:41:49.056784 kernel:[ 85.570668] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056789 kernel:[ 85.570687] [drm:gen8_de_irq_handler
> [i915]] *ERROR* Fault errors on pipe A: 0x00000080
> Oct 14 18:41:49.056885 VM hypervisor: (XEN) [VT-D]DMAR:[DMA Read]
> Request device [0000:00:02.0] fault addr 4238d0a000, iommu reg =
> ffff82c00021d000
> Oct 14 18:41:49.056890 VM hypervisor: (XEN) [VT-D]DMAR: reason 06 -
> PTE Read access is not set
>
> They repeat. In the log attached to
> https://gitlab.freedesktop.org/drm/intel/-/issues/2576, they start at
> "Oct 14 18:41:49.056589" and continue until I unplug the dock around
> "Oct 14 18:41:54.801802".
>
> I've also seen similar messages when attaching the laptop's HDMI port
> to a 4k monitor. The eDP display by itself seems okay.
>
> I tried Fedora 31 & 32 live images with intel_iommu=on, so no Xen, and
> didn't see any errors
>
> This is a kernel & xen log with drm.debug=0x1e. It also includes some
> application (glass) logging when it changes resolutions which seems to
> set off the DMA faults. 5500-igfx-messages-kern-xen-glass
>
> Running xen with iommu=no-igfx disables the iommu for the i915
> graphics and no faults are reported. However, that breaks some other
> devices (Dell Latitude 7200 and 5580) giving a black screen with:
>
> Oct 10 13:24:37.022117 kernel:[ 14.884759] i915 0000:00:02.0: Failed
> to idle engines, declaring wedged!
> Oct 10 13:24:37.022118 kernel:[ 14.964794] i915 0000:00:02.0: Failed
> to initialize GPU, declaring it wedged!
>
> Any suggestions welcome.
Presumably this is with a PV dom0. What are 39b5845000 and 4238d0a000
in the machine memory map?
This smells like a missing RMRR in the ACPI tables.
~Andrew
next prev parent reply other threads:[~2020-10-15 13:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 19:28 [Intel-gfx] i915 dma faults on Xen Jason Andryuk
2020-10-14 19:28 ` Jason Andryuk
2020-10-14 19:37 ` Andrew Cooper [this message]
2020-10-14 19:37 ` Andrew Cooper
2020-10-15 11:31 ` [Intel-gfx] " Roger Pau Monné
2020-10-15 11:31 ` Roger Pau Monné
2020-10-15 15:16 ` [Intel-gfx] " Jason Andryuk
2020-10-15 15:16 ` Jason Andryuk
2020-10-15 16:38 ` Tamas K Lengyel
2020-10-15 17:13 ` Jason Andryuk
2021-02-19 17:33 ` tboot UEFI and Xen (was Re: i915 dma faults on Xen) Jason Andryuk
2020-10-16 16:23 ` [Intel-gfx] i915 dma faults on Xen Jason Andryuk
2020-10-16 16:23 ` Jason Andryuk
2020-10-21 9:58 ` [Intel-gfx] " Roger Pau Monné
2020-10-21 9:58 ` Roger Pau Monné
2020-10-21 10:33 ` [Intel-gfx] " Jan Beulich
2020-10-21 10:33 ` Jan Beulich
2020-10-21 10:51 ` [Intel-gfx] " Roger Pau Monné
2020-10-21 10:51 ` Roger Pau Monné
2020-10-21 12:45 ` [Intel-gfx] " Jason Andryuk
2020-10-21 12:45 ` Jason Andryuk
2020-10-21 12:52 ` [Intel-gfx] " Jan Beulich
2020-10-21 12:52 ` Jan Beulich
2020-10-21 13:36 ` [Intel-gfx] " Jason Andryuk
2020-10-21 13:36 ` Jason Andryuk
2020-10-21 13:59 ` [Intel-gfx] " Jan Beulich
2020-10-21 13:59 ` Jan Beulich
2021-02-19 17:30 ` [Intel-gfx] " Jason Andryuk
2021-02-19 17:30 ` Jason Andryuk
2021-02-22 10:18 ` [Intel-gfx] " Roger Pau Monné
2021-02-22 10:18 ` Roger Pau Monné
2021-02-22 12:49 ` [Intel-gfx] " Jason Andryuk
2021-02-22 12:49 ` Jason Andryuk
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=1a3b90f4-564e-84d3-fd6a-3454e8753579@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jandryuk@gmail.com \
--cc=xen-devel@lists.xenproject.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.