Bug 105331 - [snb] GPU HANG: ecode 6:0:0x86f2fffe, in chrome
Summary: [snb] GPU HANG: ecode 6:0:0x86f2fffe, in chrome
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-02 20:43 UTC by Steve Newcomb
Modified: 2019-09-25 19:10 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
GPU crash dump (2.19 MB, text/plain)
2018-03-02 20:43 UTC, Steve Newcomb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Newcomb 2018-03-02 20:43:13 UTC
Created attachment 137761 [details]
GPU crash dump

Mar  2 13:17:50 carp kernel: [156478.322197] [drm] stuck on render ring
Mar  2 13:17:50 carp kernel: [156478.323481] [drm] GPU HANG: ecode 6:0:0x86f2fffe, in chrome [5756], reason: Ring hung, action: reset
Mar  2 13:17:50 carp kernel: [156478.323484] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar  2 13:17:50 carp kernel: [156478.323486] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar  2 13:17:50 carp kernel: [156478.323488] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar  2 13:17:50 carp kernel: [156478.323490] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mar  2 13:17:50 carp kernel: [156478.323493] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mar  2 13:17:50 carp kernel: [156478.325705] drm/i915: Resetting chip after gpu hang
Comment 1 Elizabeth 2018-03-05 15:50:51 UTC
Hello, which mesa version is it? If default, could you try 17.3.6 https://www.mesa3d.org? Thank you.
Comment 2 GitLab Migration User 2019-09-25 19:10:01 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/1702.


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.