Bug 1900639 - i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
Summary: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
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-11-23 13:14 UTC by Brian J. Murrell
Modified: 2021-05-25 17:13 UTC (History)
20 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:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab drm intel issues 2024 0 None None None 2020-11-23 13:14:54 UTC

Description Brian J. Murrell 2020-11-23 13:14:55 UTC
1. Please describe the problem:
As soon as I log in and the GNOME Shell tries to start, the GPU hangs.

2. What is the Version-Release number of the kernel:
All versions > 5.6.14

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 :
Unknown.  It's been happening in many kernels.  I have to roll back to 5.6.14 to get a usable system.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes.  Simply boot a kernel > 5.6.14.

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``:
Presumably, yes.

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.
[    3.574142] i915 0000:00:02.0: [drm] PipeC fused off
[    3.574157] i915 0000:00:02.0: vgaarb: deactivate vga console
[    3.577216] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    3.589414] [drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
[    3.616442] fbcon: i915drmfb (fb0) is primary device
[    3.708859] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
[   19.677829] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 8338.767033] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8338.767035] Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
[ 8338.767035] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 8338.767092] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8341.772995] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8341.773043] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8378.773008] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8378.774993] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8384.790346] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8384.791417] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8390.813150] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8390.813978] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8396.812580] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8396.816947] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8399.784202] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8399.784671] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8405.800070] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8405.800163] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8411.816034] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8411.818195] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8414.806940] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8414.812192] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8420.826741] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8420.827625] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8426.792204] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8426.798220] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8429.798311] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8429.799985] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8435.814342] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8435.815930] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8441.831924] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8441.836754] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8444.823371] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8444.823487] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8450.787492] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8450.788712] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8456.807788] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8456.814258] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8459.815809] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8459.816391] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8465.831703] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8465.834990] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8490.791873] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8490.793799] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8496.807663] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8496.809380] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8502.798842] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8502.798889] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8508.775461] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79
[ 8508.775581] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8685.770942] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8685.773476] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8688.778915] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd
[ 8688.778966] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 8696.780037] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in gnome-shell [3013]
[ 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 rc

This issue is reported upstream at https://gitlab.freedesktop.org/drm/intel/-/issues/2024 with a patch to fix it at https://patchwork.freedesktop.org/patch/395580/?series=82783&rev=1.

Can we please have this applied to the current F32 kernel?

Comment 1 Brian J. Murrell 2020-12-01 09:40:25 UTC
Looks like I duplicated my own bug #1886438.  Probably due to forgetting that I had opened one since there was absolutely no response to it whatsoever (in addition to the lack of response to this one).

In any case, can we please get some kind of response anyone?

FWIW, I tried to add needinfo for kernel-maint but BZ told me that account is disabled[1], hence the wide needinfo request.  This needs to get fixed and the total lack of response from two tickets opened about it, both including upstream reports and one including a patch is just distressing.

[1] It's also kind of distressing that tickets are assigned to a disabled account to which needinfo cannot be requested.

Comment 2 Justin M. Forbes 2020-12-02 15:38:13 UTC
Sorry, as there is only me managing fedora bugs, I don't typically respond to everything submitted, but I do see them and follow them. I have been following this for a while, but upstream seems to be ignoring that patch for some reason.  It has not been included in a pull request to linus and doesn't even seem to be in drm-next yet. As soon as it is, I can pull it in.

Comment 3 Brian J. Murrell 2020-12-07 12:25:46 UTC
> but upstream seems to be ignoring that patch for some reason

Can you define who upstream is this case and I will see if I can chase them?

Comment 4 Justin M. Forbes 2020-12-07 15:06:56 UTC
I would ping the author, Chris Wilson, he should be able to get it through.   Likely he just hasn't noticed it is not moving as he is working on other bugs.

Comment 5 Brian J. Murrell 2021-01-14 15:47:54 UTC
Upstream issue has been closed with a patch being submitted:

https://gitlab.freedesktop.org/drm/intel/-/issues/2024#note_755162

Can this patch be integrated into Fedora ASAP now?

Comment 6 Fedora Program Management 2021-04-29 16:49:49 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 7 Justin M. Forbes 2021-05-25 14:06:42 UTC
This should have been fixed with 5.10.9 kernels.

Comment 8 Ben Cotton 2021-05-25 17:13:52 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.