Bug 93979 - GPU HANG: ecode 7:0:0x84dfbffe, in chromium
Summary: GPU HANG: ecode 7:0:0x84dfbffe, in chromium
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
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: 2016-02-03 09:41 UTC by Ritesh Raj Sarraf
Modified: 2017-07-24 22:43 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: GPU hang

Attachments
gpu hang sysfs (3.08 MB, text/plain)
2016-02-03 09:41 UTC, Ritesh Raj Sarraf 		no flags Details
View All

Description Ritesh Raj Sarraf 2016-02-03 09:41:50 UTC 
Created attachment 121485 [details]
gpu hang sysfs

I have an INtel Haswell chipset and I've now been frequently running into this GPU hang issue.

[15012.843308] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[15016.375660] [drm] stuck on render ring
[15016.377093] [drm] GPU HANG: ecode 7:0:0x84dfbffe, in chromium [4778], reason: Ring hung, action: reset
[15016.377096] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[15016.377098] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[15016.377100] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[15016.377102] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[15016.377104] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[15016.379009] drm/i915: Resetting chip after gpu hang
2016-02-03 / 15:07:55 ♒♒♒  ☺
Comment 1 Ritesh Raj Sarraf 2016-07-01 21:36:37 UTC 
Not seen anymore with newer stack.

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.