Bug 91201 (taro)

Summary: GPU HANG: ecode 3:0:0x16dfffc1, in Xorg [332], reason: Ring hung, action: reset
Product: DRI Reporter: taro <r79616e00>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
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 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: I915G i915 features: GPU hang
Attachments:
Description Flags
Xorg.0.log
none
/sys/class/drm/card0/error
none
Full dmesg none

Description taro 2015-07-02 22:19:35 UTC
After a recent system update and reboot, the system has started freezing briefly, followed by a blank screen for a few seconds, followed by the desktop returning but with graphical errors. Dmesg indicates a GPU hang. This process repeats until the GPU hangs too fast resulting in a banning error message. The initial glitching happens again after every reboot but seems to occur more frequently when Firefox is open.


CPU on the machine is an Intel(R) Pentium(R) 4 CPU 3.00GHz, 2992 MHz, and the graphics card is an Intel 915 G.

Kernel is 4.0.7-2 on Arch. The driver being used is xf86-video-intel 1:2.99.917+364+gb24e758-1, build date: 2015-06-18 12:19 UTC. 

I've attached the results of dmesg. I'll also post Xorg.0.log and /sys/class/drm/card0/error.

(PS This is my first time filing a bug report. Apologies in advance for any errors or missing information.)
Comment 1 taro 2015-07-02 22:20:53 UTC
Created attachment 116896 [details]
Xorg.0.log

Attached Xorg.0.log.
Comment 2 taro 2015-07-02 22:22:45 UTC
Created attachment 116897 [details]
/sys/class/drm/card0/error

Attached
/sys/class/drm/card0/error
Comment 3 taro 2015-07-02 22:23:57 UTC
Created attachment 116898 [details]
Full dmesg

It seems like dmesg didn't attach the first time, so here it is.
Comment 4 Chris Wilson 2015-07-03 07:43:21 UTC

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

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.