Bug 92130 - GPU HANG: ecode 3:0:0x2b4fffc5, in Xorg [1461], reason: Ring hung, action: reset
Summary: GPU HANG: ecode 3:0:0x2b4fffc5, in Xorg [1461], reason: Ring hung, action: reset
Status: CLOSED DUPLICATE of bug 90841
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-26 21:56 UTC by Dave Gilbert
Modified: 2017-07-24 22:45 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
copy of /sys/class/drm/card0/error (758.84 KB, text/plain)
2015-09-26 21:56 UTC, Dave Gilbert
no flags Details

Description Dave Gilbert 2015-09-26 21:56:45 UTC
Created attachment 118458 [details]
copy of /sys/class/drm/card0/error

Got a hang opening a webpage and it recovered and told me to report it; this is on Ubuntu Wily kernel 4.2.0-7-generic #7-ubuntu (64 bit)

GPU:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Logs show:

[37345.820041] [drm] stuck on render ring
[37345.821100] [drm] GPU HANG: ecode 3:0:0x2b4fffc5, in Xorg [1461], reason: Ring hung, action: reset
[37345.821103] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[37345.821106] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[37345.821114] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[37345.821116] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[37345.821118] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[37346.096608] drm/i915: Resetting chip after gpu hang

error log attached.

While it's recovered after the crash it's not very happy; I'm seeing corruptions all over the screen

Dave
Comment 1 Chris Wilson 2015-12-30 21:43:18 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.