Bug 1956157 - Display corruption on resume (nouveau) Thinkpad T510
Summary: Display corruption on resume (nouveau) Thinkpad T510
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-03 04:46 UTC by Asif Youssuff
Modified: 2021-05-12 19:29 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)
image of corruption (226.66 KB, image/jpeg)
2021-05-03 04:46 UTC, Asif Youssuff
no flags Details
dmesg logs (510.15 KB, text/plain)
2021-05-03 04:53 UTC, Asif Youssuff
no flags Details

Description Asif Youssuff 2021-05-03 04:46:15 UTC
Created attachment 1778824 [details]
image of corruption

1. Please describe the problem:

I noticed during the 5.12 series that resuming my Thinkpad T510 resulted in display corruption. See camera image attached. 

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

Linux fedora 5.13.0-0.rc0.20210428gitacd3d2859453.2.fc35.x86_64 #1 SMP Wed Apr 28 17:26:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

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 :

git bisect came back with: 

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[ab0db2bd853d4a61bf440d2846b046a1d11ce027] drm/nouveau/fifo: switch to instanced constructor

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

1. Start device
2. login
3. suspend
4. resume

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 Asif Youssuff 2021-05-03 04:53:56 UTC
Created attachment 1778826 [details]
dmesg logs

Comment 2 Asif Youssuff 2021-05-12 19:29:41 UTC
Also filed upstream: https://gitlab.freedesktop.org/drm/nouveau/-/issues/95

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