Bug 1886438 - GPU HANG: ecode 7:1:85ddfffd Resetting chip for stopped heartbeat on rcs0
Summary: GPU HANG: ecode 7:1:85ddfffd Resetting chip for stopped heartbeat on rcs0
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-08 13:00 UTC by Brian J. Murrell
Modified: 2021-05-25 17:13 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:13:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (106.41 KB, text/plain)
2020-10-08 13:00 UTC, Brian J. Murrell
no flags Details
/sys/class/drm/card0/error (17.43 KB, text/plain)
2020-10-08 13:00 UTC, Brian J. Murrell
no flags Details


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab drm intel issues 2024 0 None None None 2020-10-08 13:00:22 UTC

Description Brian J. Murrell 2020-10-08 13:00:22 UTC
Created attachment 1719965 [details]
dmesg

1. Please describe the problem:
Desktop hangs for periods of time in both Wayland and Xorg.  Kernel spews:

[ 8696.784409] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8696.885587] i915 0000:00:02.0: [drm] gnome-shell[3013] context reset due to GPU hang
[ 8702.794850] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8702.799103] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 9057.801259] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [9023]
[ 9057.801310] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 9057.904403] i915 0000:00:02.0: [drm] Xorg[9023] context reset due to GPU hang
[ 9063.753362] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [9023]
[ 9063.753413] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 9063.855312] i915 0000:00:02.0: [drm] Xorg[9023] context reset due to GPU hang
[ 9069.768753] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 9069.773305] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0

when this happens.

2. What is the Version-Release number of the kernel:
5.8.13-200.fc32.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes, worked on Fedora 31.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes, simply run Fedora 32 on a machine with a:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Error: Unknown repo: 'rawhide'

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Done, as well as attaching the contents of /sys/class/drm/card0/error

Comment 1 Brian J. Murrell 2020-10-08 13:00:55 UTC
Created attachment 1719966 [details]
/sys/class/drm/card0/error

Comment 2 Brian J. Murrell 2020-10-08 13:15:36 UTC
I had to roll back to 5.5.15-200.fc31.x86_64 to work-around this issue.  Who knows what CVEs exist in that kernel, which makes this issue a security issue.

Comment 3 Fedora Program Management 2021-04-29 16:49:44 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 4 Ben Cotton 2021-05-25 17:13:43 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.