Bug 91440 - [drm] GPU HANG: ecode 8:0:0x00d8f1ec, in mpv/vo [1533], reason: Ring hung, action: reset
Summary: [drm] GPU HANG: ecode 8:0:0x00d8f1ec, in mpv/vo [1533], reason: Ring hung, ac...
Status: CLOSED WONTFIX
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: 2015-07-23 20:45 UTC by kevinlekiller
Modified: 2017-03-03 16:46 UTC (History)
1 user (show)

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


Attachments
Compressed GPU crash dump file. (448.14 KB, text/plain)
2015-07-23 20:45 UTC, kevinlekiller
no flags Details

Description kevinlekiller 2015-07-23 20:45:42 UTC
Created attachment 117324 [details]
Compressed GPU crash dump file.

Crashed while switching from windowed to full-screen (can reproduce, happens about once in 10 times of switching between windowed and full-screen), the screen goes black, I'm thrown back to the login manager.

Linux kevin-nuc 4.1.2-1-MANJARO #1 SMP PREEMPT Sat Jul 11 00:00:34 UTC 2015 x86_64 GNU/Linux

CPU: Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz

GPU: Intel HD 5500 (VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09))

GPU crash dump is attached, compressed (3.2MB uncompressed).

Log info follows:

[drm] stuck on render ring
[drm] GPU HANG: ecode 8:0:0x00d8f1ec, in mpv/vo [1533], reason: Ring hung, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
Comment 1 kevinlekiller 2015-07-23 20:55:37 UTC
More info, (didn't see the "How to report bugs" until after, although most of this info is in the first comment).

System architecture: x86_64
Kernel version: 4.1.2-1-MANJARO
Distribution: Manjaro XFCE x64 with systemd version 222
Machine: Intel NUC NUC5i3RYH
Display connector: DP1 (displayport)
Comment 2 yann 2017-02-24 08:14:52 UTC
We seem to have neglected the bug a bit, apologies.

kevinlekiller@gmail.com, since There were improvements pushed in kernel & mesa that will benefit to your system, so please re-test with latest kernel & mesa and mark as REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log) and RESOLVED/* if you cannot reproduce.
Comment 3 yann 2017-03-03 16:46:45 UTC
(In reply to yann from comment #2)
> We seem to have neglected the bug a bit, apologies.
> 
> kevinlekiller@gmail.com, since There were improvements pushed in kernel &
> mesa that will benefit to your system, so please re-test with latest kernel
> & mesa and mark as REOPENED if you can reproduce (and attach fresh gpu error
> dump & kernel log) and RESOLVED/* if you cannot reproduce.

Timeout. Assuming that this is not occurring anymore. If this issue happens again, re-test with latest kernel & mesa version and REOPEN if you can reproduce (and attach fresh gpu error dump & kernel log)


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.