Bug 79222 - [gen4] Invalid GTT entry during host access
Summary: [gen4] Invalid GTT entry during host access
Status: CLOSED DUPLICATE of bug 53385
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 80733 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-05-25 18:54 UTC by Peter Klotz
Modified: 2017-07-24 22:54 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Dump saved in /sys/class/drm/card0/error (gzip compressed) (187.23 KB, text/plain)
2014-05-25 18:54 UTC, Peter Klotz
no flags Details

Description Peter Klotz 2014-05-25 18:54:44 UTC
Created attachment 99791 [details]
Dump saved in /sys/class/drm/card0/error (gzip compressed)

Using Kaffeine together with a Terratec Cinergy DVB-T USB stick resulted in a GPU crash:

[248572.055652] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[248572.055657] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[248572.055659] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[248572.055660] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[248572.055661] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[248572.056966] i915: render error detected, EIR: 0x00000010
[248572.056970] i915:   IPEIR: 0x00000000
[248572.056972] i915:   IPEHR: 0x01000000
[248572.056973] i915:   INSTDONE_0: 0xfffffffe
[248572.056975] i915:   INSTDONE_1: 0xffffffff
[248572.056976] i915:   INSTDONE_2: 0x00000000
[248572.056978] i915:   INSTDONE_3: 0x00000000
[248572.056979] i915:   INSTPS: 0x0001e000
[248572.056981] i915:   ACTHD: 0xc3c0c6b8
[248572.056983] i915: page table error
[248572.056984] i915:   PGTBL_ER: 0x00000001
[248572.056988] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

OS: Arch Linux x86_64
Kernel: 3.14.4
Xorg: 1.15.1
Comment 1 Chris Wilson 2014-05-25 19:03:24 UTC
It should not be a critical bug, it should not be fatal to the GPU, just a nuisance. It is not clear whether these are erroneous faults or some corner case we are not handling correctly - unfortunately the GPU doesn't actually report the faulting address - though maybe inspecting current->comm could name the suspect driver.
Comment 2 Chris Wilson 2014-06-30 21:16:39 UTC
*** Bug 80733 has been marked as a duplicate of this bug. ***
Comment 3 Chris Wilson 2015-01-27 12:33:32 UTC

*** This bug has been marked as a duplicate of bug 53385 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.