Bug 93930 - [HSW] Filing "GPU HANG" Bug (as requested by dmesg)
Summary: [HSW] Filing "GPU HANG" Bug (as requested by dmesg)
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) 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-01-29 21:20 UTC by Kenneth C
Modified: 2016-10-21 13:59 UTC (History)
1 user (show)

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

Attachments
/sys/class/drm/card0/error (435.88 KB, text/plain)
2016-01-29 21:20 UTC, Kenneth C 		no flags Details
View All

Description Kenneth C 2016-01-29 21:20:00 UTC 
Created attachment 121396 [details]
/sys/class/drm/card0/error

Per dmesg:

----
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.086615] [drm] stuck on render ring
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087510] [drm] GPU HANG: ecode 7:0:0xa8603fff, in chrome [8147], reason: Ring hung, action: reset
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087511] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087512] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087512] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087513] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.087513] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jan 29 12:44:49 tosh-p75a kernel: [ 9986.089638] drm/i915: Resetting chip after gpu hang
----
Comment 1 Kenneth C 2016-01-29 21:20:51 UTC 
Attachment is .gzipped
Comment 2 yann 2016-09-13 14:22:23 UTC 
Kenneth, sorry for the late reply. Can you share a little bit more about context when this hung happens in Chrome?
Is it still occurring, even after upgrading your kernel? Do you have the kernel log (please add "drm.debug=0xe log_buf_len=1M" in your boot command line)?
Comment 3 yann 2016-10-21 13:58:53 UTC 
(In reply to yann from comment #2)
> Kenneth, sorry for the late reply. Can you share a little bit more about
> context when this hung happens in Chrome?
> Is it still occurring, even after upgrading your kernel? Do you have the
> kernel log (please add "drm.debug=0xe log_buf_len=1M" in your boot command
> line)?

Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.

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.