Bug 44478

Summary: [GM965] GPU crash
Product: xorg Reporter: celejar
Component: Driver/intelAssignee: Chris Wilson <chris>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.5 (2009.10)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log from crashed X session
none
Output of intel_gpu_dump after crash
none
vbios dump
none
last batch buffer none

Description celejar 2012-01-04 20:56:58 UTC
Occasionally, my X session freezes - no changes to display, except for mouse pointer, which seems to work fine, although mouse clicks don't seem to do anything. I can switch to VT1, and then X eventually bails. Log is filled with many lines like these:

(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Resource temporarily unavailable.
(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error.
(WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error

Chipset:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
Comment 1 celejar 2012-01-04 21:07:35 UTC
Sorry, hit enter by mistake.

Linux lizzie 3.1.7 #6 SMP Tue Jan 3 21:40:11 EST 2012 x86_64 GNU/Linux
Debian Stable with Backports
OpenGL version string: 2.1 Mesa 7.7.1
Thinkpad T61
Comment 2 celejar 2012-01-04 21:08:29 UTC
Created attachment 55150 [details]
Xorg log from crashed X session
Comment 3 celejar 2012-01-04 21:10:42 UTC
Created attachment 55151 [details]
Output of intel_gpu_dump after crash
Comment 4 celejar 2012-01-04 21:11:35 UTC
Created attachment 55152 [details]
vbios dump
Comment 5 celejar 2012-01-04 21:12:24 UTC
Created attachment 55153 [details]
last batch buffer
Comment 6 Chris Wilson 2012-01-05 02:47:28 UTC
Invalid upper limits on state addresses, fixed in 2.14.

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.