Bug 97030 - GPU HANG: ecode 7:0:0x85dffffd, in X [3116], reason: Ring hung, action: reset
Summary: GPU HANG: ecode 7:0:0x85dffffd, in X [3116], reason: Ring hung, action: reset
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
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-07-21 19:28 UTC by Martin Doucha
Modified: 2017-07-27 16:52 UTC (History)
1 user (show)

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


Attachments
dmesg output after the freeze (965 bytes, text/plain)
2016-07-21 19:28 UTC, Martin Doucha
no flags Details
GPU crash dump (429.23 KB, application/gzip)
2016-07-21 19:30 UTC, Martin Doucha
no flags Details
X.org server log from when the freeze happened (22.90 KB, text/plain)
2016-07-21 19:31 UTC, Martin Doucha
no flags Details

Description Martin Doucha 2016-07-21 19:28:47 UTC
Created attachment 125241 [details]
dmesg output after the freeze

My machine froze for a few seconds while playing a WebGL Unity game in web browser (Firefox). I've been playing the game for months without such problem so it's very likely I won't be able to reproduce this. dmesg report, GPU crash dump and X server log are attached.

My system is Gentoo Linux running on HP ProBook 450 (about 2 years old) with Intel Core i5 CPU. The machine also has additional AMD Radeon GPU which I don't use. I had no external displays connected when the freeze happened (only the built-in laptop display was active).

uname -mr: 4.4.2-gentoo x86_64
Comment 1 Martin Doucha 2016-07-21 19:30:22 UTC
Created attachment 125242 [details]
GPU crash dump
Comment 2 Martin Doucha 2016-07-21 19:31:22 UTC
Created attachment 125243 [details]
X.org server log from when the freeze happened
Comment 3 Chris Wilson 2016-07-21 19:54:23 UTC
There's nothing unusual in the batch that took the blame either. First thought is along the lines of memory/GTT placement. No testable hypothesis atm.
Comment 4 Jari Tahvanainen 2017-03-08 10:33:29 UTC
Chris - do you see a relation between this and Bug 88411? Both are for (4.4.x) kernel, other one reported against HSW though...
Comment 5 Jari Tahvanainen 2017-04-10 11:15:16 UTC
Martin - is problem still valid with the latest kernel version (preferable drm-tip from git://anongit.freedesktop.org/git/drm-tip)? If yes then please change status to REOPENED and attach newest data, like you did originally.
Comment 6 Jari Tahvanainen 2017-05-23 13:19:38 UTC
Timeout - marking resolved+worksforme. Please reopen the bug if problem still persists with the latest kernels (preferable from drm-tip).


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.