Bug 1436908 - GPU HANG: ecode 8:0:0x86dffffd, in gnome-shell [12016], reason: Hang on render ring, action: reset
Summary: GPU HANG: ecode 8:0:0x86dffffd, in gnome-shell [12016], reason: Hang on rende...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-29 01:37 UTC by Han Han
Modified: 2018-05-29 12:33 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:33:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The gpu crash dump (26.10 KB, text/plain)
2017-03-29 01:37 UTC, Han Han
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1457669 0 unspecified CLOSED [drm] GPU HANG: ecode 8:0:0x86dffffd, in gnome-shell 2021-02-22 00:41:40 UTC

Internal Links: 1457669

Description Han Han 2017-03-29 01:37:34 UTC
Created attachment 1267205 [details]
The gpu crash dump

Description of problem:
As subject

Version-Release number of selected component (if applicable):
kernel-4.11.0-0.rc3.git0.2.fc26.x86_64

How reproducible:


Steps to Reproduce:
# lspci -v
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device 2227
        Flags: bus master, fast devsel, latency 0, IRQ 47
        Memory at f0000000 (64-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 3000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915
        Kernel modules: i915


GPU of i915 sometimes hangs when using gnome:
Dmesg:
[  218.485178] DMAR: DRHD: handling fault status reg 3
[  218.485184] DMAR: [DMA Write] Request device [00:02.0] fault addr fb4c6000 [fault reason 23] Unknown
[  218.485189] DMAR: DRHD: handling fault status reg 3
[  218.485193] DMAR: [DMA Write] Request device [00:02.0] fault addr fb4de000 [fault reason 23] Unknown
[  218.485196] DMAR: DRHD: handling fault status reg 2
[  218.485199] DMAR: [DMA Write] Request device [00:02.0] fault addr fb500000 [fault reason 23] Unknown
[  218.485201] DMAR: DRHD: handling fault status reg 2
[  218.485203] DMAR: [DMA Write] Request device [00:02.0] fault addr fb4f6000 [fault reason 23] Unknown
[  218.485205] DMAR: DRHD: handling fault status reg 2
[  218.485208] DMAR: [DMA Write] Request device [00:02.0] fault addr fb4fc000 [fault reason 23] Unknown
[  218.485210] DMAR: DRHD: handling fault status reg 2
[  218.485212] DMAR: [DMA Write] Request device [00:02.0] fault addr fb50f000 [fault reason 23] Unknown
[  218.485214] DMAR: DRHD: handling fault status reg 2
[  218.485216] DMAR: [DMA Write] Request device [00:02.0] fault addr fb507000 [fault reason 23] Unknown
[  227.527793] [drm] GPU HANG: ecode 8:0:0x86dffffd, in gnome-shell [12016], reason: Hang on render ring, action: reset
[  227.527795] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  227.527795] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  227.527796] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  227.527796] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  227.527797] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  227.527827] drm/i915: Resetting chip after gpu hang
[  232.068114] do_trap: 342 callbacks suppressed
[  232.068116] traps: baobab[13622] trap int3 ip:7fc848dcdde1 sp:7fff84809480 error:0
[  232.068119]  in libglib-2.0.so.0.5200.0[7fc848d7e000+110000]
[  235.523626] drm/i915: Resetting chip after gpu hang
[  243.523774] drm/i915: Resetting chip after gpu hang
[  254.532149] drm/i915: Resetting chip after gpu hang
[  262.532278] drm/i915: Resetting chip after gpu hang


2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Laura Abbott 2017-03-29 16:50:06 UTC
Moving for the graphics team to take a look

Comment 2 Fedora End Of Life 2018-05-03 08:14:35 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 12:33:16 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.