Bug 1783667 - i915 GPU hang
Summary: i915 GPU hang
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-14 15:56 UTC by rvcsaba
Modified: 2020-03-10 20:13 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-04 16:22:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg, lscpu, lspci, /sys/class/drm/card0/error (22.65 KB, application/x-xz)
2019-12-14 15:56 UTC, rvcsaba
no flags Details

Description rvcsaba 2019-12-14 15:56:46 UTC
Created attachment 1645201 [details]
dmesg, lscpu, lspci, /sys/class/drm/card0/error

1. Please describe the problem:

i915 GPU hang, display freeze. Please see an attachment!


2. What is the Version-Release number of the kernel:

5.4.2-300.fc31.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 :

I detected this problem first in 5.4.2, but GPU hang only once with 5.3.15.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Just use my computer.


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``:


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


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.

Comment 1 rvcsaba 2020-01-08 19:48:02 UTC
I tested with 5.4.8, but same problem. :( Latest good kernel is 5.3.18.

Comment 2 Justin M. Forbes 2020-03-03 16:20:39 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.

Comment 3 rvcsaba 2020-03-04 08:57:17 UTC
5.5.7-200 solved this problem.

Comment 4 Justin M. Forbes 2020-03-04 16:22:22 UTC
Thank you for letting us know.


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