Bug 78531

Summary: GPU crash
Product: DRI Reporter: Benjamin Baumgärtner <bb>
Component: DRM/IntelAssignee: Imre Deak <imre.deak>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
cat /sys/class/drm/card0/error > error.txt none

Description Benjamin Baumgärtner 2014-05-10 16:05:18 UTC
Created attachment 98822 [details]
cat /sys/class/drm/card0/error > error.txt

Frequently, the screen hangs for 20-40 secs, and/or weird output is on the screen. Sometimes, the desktop recovers automatically, sometimes a restart of the xserver is required. That happens especially when using the Unity desktop, seldomly using LXDE. With Unity, it happens ~every 2 minutes.

Kernel ring buffer says:

[  256.978995] [drm] stuck on render ring
[  256.979005] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  256.979006] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  256.979007] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  256.979008] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  256.979008] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  262.980759] [drm] stuck on render ring
[  262.980804] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
[  268.994551] [drm] stuck on render ring
[  275.996616] [drm] stuck on render ring
[  324.999123] [drm] stuck on render ring
[  336.014394] [drm] stuck on render ring
[  336.022431] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
[  342.016164] [drm] stuck on render ring
[  363.022392] [drm] stuck on render ring
[  369.024165] [drm] stuck on render ring
[  369.024295] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!

Graphics Hardware is a Pentium G2020 with Intel HD Graphics, Motherboard is a ASRock H77 Pro4-M.

$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation H77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 

$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Pentium(R) CPU G2020 @ 2.90GHz
stepping	: 9
microcode	: 0x15
cpu MHz		: 2475.875
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips	: 5787.02
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Pentium(R) CPU G2020 @ 2.90GHz
stepping	: 9
microcode	: 0x15
cpu MHz		: 2294.625
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 2
initial apicid	: 2
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips	: 5787.02
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:
Comment 1 Chris Wilson 2014-05-10 17:24:11 UTC
The decode looks like complete and utter garbage. What version of mesa?
Comment 2 Benjamin Baumgärtner 2014-05-10 17:36:45 UTC
First thing I forgot to mention: the system is Ubuntu trusty

Regarding the mesa version:

$ glxinfo | grep "Mesa"
client glx vendor string: Mesa Project and SGI
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0
OpenGL version string: 3.0 Mesa 10.1.0
Comment 3 Chris Wilson 2014-05-11 07:28:28 UTC

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

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.