Bug 1674065 - Plymouth screen garbled, wayland does not start since kernel 4.20.5 / amdgpu
Summary: Plymouth screen garbled, wayland does not start since kernel 4.20.5 / amdgpu
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
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: 2019-02-08 22:33 UTC by Dennis Wagelaar
Modified: 2019-02-25 12:09 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-25 12:09:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl --no-hostname -k for kernel-4.20.5-100.fc28.x86_64 (87.57 KB, text/plain)
2019-02-08 22:33 UTC, Dennis Wagelaar
no flags Details
journalctl --no-hostname -k for kernel-4.20.4-100.fc28.x86_64 (92.81 KB, text/plain)
2019-02-08 22:35 UTC, Dennis Wagelaar
no flags Details
journalctl --no-hostname -k for kernel-4.20.6-100.fc28.x86_64 (93.12 KB, text/plain)
2019-02-08 22:35 UTC, Dennis Wagelaar
no flags Details
journalctl --no-hostname -k for kernel-5.0.0-0.rc4.git3.1.fc30.x86_64 (90.14 KB, text/plain)
2019-02-08 22:36 UTC, Dennis Wagelaar
no flags Details
Photo of garbled plymouth boot screen (1.58 MB, image/jpeg)
2019-02-08 22:38 UTC, Dennis Wagelaar
no flags Details
Photo of garbled bootup text framebuffer (1.93 MB, image/jpeg)
2019-02-08 22:39 UTC, Dennis Wagelaar
no flags Details
Output of lshw (32.08 KB, text/plain)
2019-02-08 22:46 UTC, Dennis Wagelaar
no flags Details
Output of dmidecode (17.43 KB, text/plain)
2019-02-08 22:51 UTC, Dennis Wagelaar
no flags Details
journalctl --no-hostname -k for kernel-4.20.8-100.fc28.x86_64 (87.12 KB, text/plain)
2019-02-24 09:50 UTC, Dennis Wagelaar
no flags Details

Description Dennis Wagelaar 2019-02-08 22:33:47 UTC
Created attachment 1528242 [details]
journalctl --no-hostname -k for kernel-4.20.5-100.fc28.x86_64

1. Please describe the problem:
Starting from kernel-4.20.5-100.fc28.x86_64, the plymouth bootup screen, as well as the textual framebuffer is garbled (see attached photos), and the wayland graphical login never starts up. Instead, the monitor goes into power save (no video signal). There is no recovery from this state, and I have to power cycle the computer.

2. What is the Version-Release number of the kernel:
kernel-4.20.5-100.fc28.x86_64
kernel-4.20.6-100.fc28.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 :
All is fine on kernel-4.20.4-100.fc28.x86_64, albeit that I have to disable amdgpu dc (options amdgpu dc=0), because it causes screen flicker. It appears dc was enabled by default since kernel 4.20, whereas it was disabled by default before that.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Boot up, amdgpu dc setting does not matter.

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``:
Yes, kernel-5.0.0-0.rc4.git3.1.fc30.x86_64 exhibits the same problem.

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.

feb 08 22:50:34 kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
feb 08 22:50:34 kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing D6A0 (len 978, WS 0, PS 0) @ 0xD7EF
feb 08 22:50:34 kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing D55A (len 326, WS 0, PS 0) @ 0xD5F6

Comment 1 Dennis Wagelaar 2019-02-08 22:35:05 UTC
Created attachment 1528243 [details]
journalctl --no-hostname -k for kernel-4.20.4-100.fc28.x86_64

Comment 2 Dennis Wagelaar 2019-02-08 22:35:42 UTC
Created attachment 1528244 [details]
journalctl --no-hostname -k for kernel-4.20.6-100.fc28.x86_64

Comment 3 Dennis Wagelaar 2019-02-08 22:36:18 UTC
Created attachment 1528245 [details]
journalctl --no-hostname -k for kernel-5.0.0-0.rc4.git3.1.fc30.x86_64

Comment 4 Dennis Wagelaar 2019-02-08 22:38:28 UTC
Created attachment 1528246 [details]
Photo of garbled plymouth boot screen

Comment 5 Dennis Wagelaar 2019-02-08 22:39:39 UTC
Created attachment 1528247 [details]
Photo of garbled bootup text framebuffer

Comment 6 Dennis Wagelaar 2019-02-08 22:46:51 UTC
Created attachment 1528248 [details]
Output of lshw

Hardware:
- AMD Ryzen 1600X CPU
- Asus B350M-A PRIME motherboard, BIOS version 4207
- MSI Radeon RX 560 AERO ITX 4G OC graphics card
- Philips 276E8VJSB (4K) monitor

Comment 7 Dennis Wagelaar 2019-02-08 22:51:49 UTC
Created attachment 1528249 [details]
Output of dmidecode

Comment 8 Dennis Wagelaar 2019-02-24 09:50:22 UTC
Created attachment 1538096 [details]
journalctl --no-hostname -k for kernel-4.20.8-100.fc28.x86_64

Problem still occurs with kernel-4.20.8-100.fc28.x86_64

Comment 9 Dennis Wagelaar 2019-02-24 10:29:05 UTC
Reported upstream bug at https://bugzilla.kernel.org/show_bug.cgi?id=202667

Comment 10 Dennis Wagelaar 2019-02-25 12:09:40 UTC
See upstream bug for discussion.


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