Bug 93482

Summary: GPU HANG, Kicking stuck semaphore on render ring
Product: DRI Reporter: James <theholyettlz>
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: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
full dmesg after incident
none
crashdump from sysfs
none
Xorg log none

Description James 2015-12-23 09:29:26 UTC
Created attachment 120662 [details]
full dmesg after incident

I was doing some ordinary browsing activity and the screen froze for a few seconds, before returning to normal. When I checked dmesg I found:

[125107.835253] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue
[125107.835256] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[125107.835257] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[125107.835257] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[125107.835258] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[125107.835259] [drm] GPU crash dump saved to /sys/class/drm/card0/error

Intel HD 3000 graphics on an i7-2760QM. Using Fedora 23, kernel and driver versions:

kernel-4.2.7-300.fc23.x86_64
xorg-x11-drv-intel-2.99.917-16.20150729.fc23.x86_64
mesa-dri-drivers-11.0.6-1.20151122.fc23.x86_64

Attached below: full dmesg output, Xorg log, crash dump.
Comment 1 James 2015-12-23 09:30:23 UTC
Created attachment 120663 [details]
crashdump from sysfs
Comment 2 James 2015-12-23 09:30:46 UTC
Created attachment 120664 [details]
Xorg log
Comment 3 Chris Wilson 2015-12-23 09:31:03 UTC

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

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.