Bug 1984686

Summary: wayland black screen with white flashes after kernel 5.13.4-200
Product: [Fedora] Fedora Reporter: Gerald Cox <gbcox>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 34CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-21 22:41:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
kernel log none

Description Gerald Cox 2021-07-21 21:14:12 UTC
1. Please describe the problem:
After upgrade to kernel 5.13.4-200, following display manager (either gdm or sddm) system shows black screen with intermittent white flashes.  This happens when trying to use either Wayland GNOME or Wayland Plasma.  Does not occur when using X11. 


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


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, previous versions worked fine.  If I boot using the 5.12 kernel things appear to work perfectly.


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

Issue can be reproduced ever time when booting the 5.13.4-200 kernel.  GDM or SDDM display managers exhibit the exact same error.  Also, doesn't matter if you are using GNOME Wayland or Plasma Wayland.  Error occurs every time.  Backing out to the previous kernel (5.12) resolves issue.


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

Haven't tried.  Will do and update the ticket.


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.


Will get a fresh error log and attach.

Comment 1 Gerald Cox 2021-07-21 21:34:51 UTC
Created attachment 1804269 [details]
kernel log

Comment 2 Gerald Cox 2021-07-21 21:56:58 UTC
Verified that issue also occurs with:

kernel-core-5.14.0-0.rc2.23.fc35.x86_64
kernel-modules-5.14.0-0.rc2.23.fc35.x86_64
kernel-5.14.0-0.rc2.23.fc35.x86_64
kernel-modules-extra-5.14.0-0.rc2.23.fc35.x86_64

P.S. In order to install the rawhide kernel I had to disable the gpgkey checking.  
Appears that "install fedora-repos-rawhide" didn't install the correct keys or
that the fc35 kernel isn't signed properly.

Comment 3 Gerald Cox 2021-07-21 22:41:06 UTC

*** This bug has been marked as a duplicate of bug 1981039 ***