Created attachment 1755386 [details] "journal -b 0" from boot that fails 1. Please describe the problem: After upgrade yesterday, booting leaves a blank screen instead of GDM screen. If I boot to previous kernel (5.10.9-201) everything works. Note: I can SSH in. That's how I got the logs. 2. What is the Version-Release number of the kernel: 5.10.12-200.fc33 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, it worked previously. The problem appeared with an update to 5.10.12-200.fc33 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Boot with 5.10.12-200.fc33 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``: Could not install: "The GPG keys listed for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package." 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.
Created attachment 1755387 [details] "journalctl -b -1" from a boot that worked (previous kernel) There are a few interesting messages in the failing log but not the successful one. The most repeated: gnome-shell[1068]: Failed to post KMS update: Page flip of 58 failed, and no mode set available Earlier, the failing log has: Feb 06 06:47:38 localhost.localdomain kernel: fbcon: amdgpudrmfb (fb0) is primary device Feb 06 06:47:38 localhost.localdomain kernel: [drm] DC global validation failure: Bandwidth validation failure (BW and Watermark) (13) Feb 06 06:47:38 localhost.localdomain kernel: Console: switching to colour frame buffer device 480x135 Feb 06 06:47:38 localhost.localdomain kernel: [drm] DC global validation failure: Bandwidth validation failure (BW and Watermark) (13) Feb 06 06:47:38 localhost.localdomain kernel: amdgpu 0000:04:00.0: [drm] fb0: amdgpudrmfb frame buffer device Feb 06 06:47:38 localhost.localdomain kernel: [drm] DC global validation failure: Bandwidth validation failure (BW and Watermark) (13) Feb 06 06:47:38 localhost.localdomain kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 The succeeding log has instead: Feb 06 06:38:19 localhost.localdomain kernel: fbcon: amdgpudrmfb (fb0) is primary device Feb 06 06:38:19 localhost.localdomain kernel: Console: switching to colour frame buffer device 480x135 Feb 06 06:38:19 localhost.localdomain kernel: amdgpu 0000:04:00.0: [drm] fb0: amdgpudrmfb frame buffer device Feb 06 06:38:19 localhost.localdomain kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Created attachment 1755767 [details] "journalctl -b" from failure in 5.10.13-200.fc33 I've just tested with the new kernel from updates (5.10.13-200.fc33). It too fails with a blanks screen instead of a GDM screen.
same problem with 5.10.14-200.fc33.x86_64
same problem with 5.10.16-200.fc33.x86_64
5.9.14-200.fc33.x86_64 works. It is the latest 5.9 kernel that I found on Koji. https://koji.fedoraproject.org/koji/buildinfo?buildID=1657548 It seems likely that the 5.9 to 5.10 transition is where things broke. How should I proceed?
I tried sudo dnf update --enablerepo=rawhide --nogpgcheck kernel (thank karuboniru[m] from IRC) This installed kernel 5.11.0-155.fc35.x86_64. Same failure mode.
Created attachment 1762110 [details] "journalctl -b" from failure using 5.11.0-155.fc35.x86_64
I'm still having this problem, even though I keep updating to new Fedora kernels. The first sign of trouble appears when fbcon tries to flip to amdgpudrmfb. About 3 seconds into the boot. May 22 12:31:40 kernel: [drm] DC global validation failure: Bandwidth validation failure (BW and Watermark) (13) The display if an UltraHD TV. The computer has no trouble driving it under 4.9 How can I convince later kernels that the monitor can be driven?
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.