Bug 86629 - [snb] GPU HANG: ecode 0:0x85fffffc, in chrome [30684], reason: Ring hung, action: reset
Summary: [snb] GPU HANG: ecode 0:0x85fffffc, in chrome [30684], reason: Ring hung, act...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-23 14:18 UTC by Sami Farin
Modified: 2019-09-25 18:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
drm.error.txt.xz (109.33 KB, text/plain)
2014-11-23 14:18 UTC, Sami Farin 		Details
drm.error.txt.xz (109.33 KB, application/octet-stream)
2014-11-23 14:20 UTC, Sami Farin 		Details
Show Obsolete (1) View All

Description Sami Farin 2014-11-23 14:18:32 UTC 
Created attachment 109899 [details]
drm.error.txt.xz

2014-11-23 16:05:43.696710223 [1108752.697015] [drm] stuck on render ring
2014-11-23 16:05:43.696711635 [1108752.698089] [drm] GPU HANG: ecode 0:0x85fffffc, in chrome [30684], reason: Ring hung, action: reset

I was using google maps in chrome.
After restart chrome seems to work ok.

Linux 3.18.0-rc4, libdrm-2.4.58, google-chrome-stable 39.0.2171.65
SNA initialized with Sandybridge (gen6, gt2) backend
Comment 1 Sami Farin 2014-11-23 14:20:46 UTC 
Created attachment 109900 [details]
drm.error.txt.xz
Comment 2 Matt Turner 2017-03-22 02:36:18 UTC 
Sorry no one ever investigated your bug.

Please reopen if you can still reproduce with Mesa 17.0.
Comment 3 GitLab Migration User 2019-09-25 18:52:55 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1464.

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.