My desktop machine was upgraded to Fedora 28 shortly after release, and was working fine. After upgrading to 4.17 kernel, the machine appeared to freeze on boot - immediately after selecting an item from the grub menu, the screen goes black, and never recovers... no splash screen nor login prompt. Reverting to the 4.16 kernel fixed the problem, until that was uninstalled by an upgrade. Further research has found that the system boots successfully under 4.17 kernels if I pass amdgpu.dc=0 via grub. Hardware wise, the processor is an AMD A10-7850k, and the GPU is an AMD RX-470. I'm not sure what information you need here, but I'm going to provide the output of lspci, dmesg, and /proc/cpuinfo for a successful boot. If you need me to try and get some kind of logging from the failed boot, no problem, but you'll need to tell me how. Oh, and I've found a few maybe-related bugs on here, notably #1583443. As such, I've tried the dracut firmware install command suggested there, to no avail.
Created attachment 1459376 [details] Contents of /proc/cpuinfo on successful boot
Created attachment 1459377 [details] Output of dmesg on successful boot
Created attachment 1459378 [details] Output of lspci on successful boot
Did you manually add amdgpu.dc=0 to the boot parameters?
(In reply to Germano Massullo from comment #4) > Did you manually add amdgpu.dc=0 to the boot parameters? Not sure what you mean? As I said in the initial report, it boots fine if I pass amdgpu.dc=0 on the kernel command line...
Then I think your bugreport and mine, may be related https://bugzilla.redhat.com/show_bug.cgi?id=1624607
Maybe, but there's not much similarity in symptoms... I suspect all they have in common is that they relate to the AMDGPU DC functionality becoming the default in the 4.17 kernel... turning it off via the kernel parameter essentially reverts to the behaviour that worked with 4.16. It'd be nice to get some comment from an expert, but unfortunately none has commented on this bug in the month and a half since I logged it... :(
(In reply to Simon Geard from comment #7) > Maybe, but there's not much similarity in symptoms... I suspect all they > have in common is that they relate to the AMDGPU DC functionality becoming > the default in the 4.17 kernel... turning it off via the kernel parameter > essentially reverts to the behaviour that worked with 4.16. That is exactly the problem > It'd be nice to get some comment from an expert, but unfortunately none has > commented on this bug in the month and a half since I logged it... :( Driver bugs should be reported directly to upstream developers like I have done https://bugs.freedesktop.org/show_bug.cgi?id=107465 (downstream https://bugzilla.redhat.com/show_bug.cgi?id=1624607)
Logged upstream as: https://bugs.freedesktop.org/show_bug.cgi?id=107793
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.