Bug 103290 - [ilk] GPU HANG: ecode 5:0:0xfe7dfe7f, in plasmashell [1624], reason: Hang on render ring, action: reset
Summary: [ilk] GPU HANG: ecode 5:0:0xfe7dfe7f, in plasmashell [1624], reason: Hang on ...
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: 2017-10-16 08:57 UTC by vkosharskyi
Modified: 2018-04-25 08:15 UTC (History)
1 user (show)

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


Attachments
Saved GPU crash dump (857.31 KB, text/plain)
2017-10-16 08:57 UTC, vkosharskyi
no flags Details

Description vkosharskyi 2017-10-16 08:57:36 UTC
Created attachment 134860 [details]
Saved GPU crash dump

[drm] GPU HANG: ecode 5:0:0xfe7dfe7f, in plasmashell, reason: Hang on render ring, 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

Intel® HD Graphics 

00:02.0 [8086:0046] VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

CPU Intel(R) Core(TM) i3 CPU M 380
Comment 1 vkosharskyi 2017-10-16 09:06:44 UTC
Machine: Dell Vostro 1540

# uname -m
x86_64
# uname -r
4.4.87-25-default
# cat /etc/issue
Welcome to openSUSE Leap 42.
Comment 2 vkosharskyi 2017-10-16 09:07:34 UTC
kernel flags:
i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 pcie_aspm=force
Comment 3 Chris Wilson 2017-10-16 09:18:47 UTC
This is an odd one. It looks like bug 99671 - executing an old batch, but it may just be hitting the end of the address space. Nevertheless the most prudent course of action is to update the kernel.
Comment 4 Jani Saarinen 2018-03-29 07:10:43 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 5 Jani Saarinen 2018-04-25 08:15:35 UTC
Closing, please re-open is issue still exists.


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.