Bug 78050 - [845g] Display B TLB: Invalid GTT PTE, switching between X and VT or using Xv
Summary: [845g] Display B TLB: Invalid GTT PTE, switching between X and VT or using Xv
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-29 00:44 UTC by Kratka
Modified: 2017-07-24 22:54 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (674.37 KB, text/plain)
2014-04-29 00:44 UTC, Kratka
no flags Details
Xorg.0.log (25.02 KB, text/plain)
2014-04-29 00:44 UTC, Kratka
no flags Details
/sys/kernel/debug/dri/0/i915_gem_gtt (after switching vt error) (16.62 KB, text/plain)
2014-05-06 23:08 UTC, Kratka
no flags Details

Description Kratka 2014-04-29 00:44:04 UTC
Created attachment 98147 [details]
/sys/class/drm/card0/error

Hi,

I'm using Arch Linux. I get this error message sometimes when switching from X to tty(s) or using mplayer (xv). The X is still stable. If I set DRI to False and NoAccel to True in xorg.conf, the message gone. But it's not a solution for me, because of the poor graphic performance.


$ dmesg:
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[21787.534947] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[21787.534950] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[21787.534952] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[21787.534954] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[21787.537835] i915: render error detected, EIR: 0x00000010
[21787.537835] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[21787.537835] i915: render error detected, EIR: 0x00000010

$ uname -srvmo
Linux 3.14.1-1-ARCH #1 SMP PREEMPT Mon Apr 14 21:01:08 CEST 2014 i686 GNU/Linux

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)


intel-dri 10.1.1-1
xf86-video-intel 2.99.911-2
xorg-server 1.15.1-1
Comment 1 Kratka 2014-04-29 00:44:57 UTC
Created attachment 98148 [details]
Xorg.0.log
Comment 2 Chris Wilson 2014-04-29 06:21:33 UTC
Can you confirm that DRI false fixes this? That would be unexpected from the symptoms at first glance.
Comment 3 Kratka 2014-04-29 23:57:04 UTC
Tested and you're right, this not necessary. Only '"NoAccel" "True"' fixed this.

The correct xorg.conf:

Section "Device"
    Identifier "card0"
    Driver "intel" 
#   Option "Dri" "False"
    Option "NoAccel" "True"
EndSection
Comment 4 Chris Wilson 2014-04-30 10:29:15 UTC
Is it always the same error for VT switching and Xv? Can you please attach /sys/kernel/debug/dri/0/i915_gem_gtt after the error?
Comment 5 Kratka 2014-05-06 23:08:45 UTC
Created attachment 98594 [details]
/sys/kernel/debug/dri/0/i915_gem_gtt (after switching vt error)
Comment 6 Kratka 2014-05-06 23:19:21 UTC
Not always. On the latest attempt to understand the bug, i run mplayer for 4-5 hours. And then my screen was black, responded to nothing, I hit SysRq + REISUB, but it didn't help. Only removing the power cable saved me. 

This single message remained:

[drm] stuck on render ring
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm:i915_reset] *ERROR* Failed to reset chip: -19
Comment 7 Rodrigo Vivi 2014-09-24 20:35:45 UTC
Could you please retest with latest -nightly?
Comment 8 Rodrigo Vivi 2015-01-15 00:17:53 UTC
timeout. Feel free to reopen if you are still able to reproduce on recent kernels updating new logs.


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.