Created attachment 292699 [details] boot log 5.8.11 fedora When using a 5.8.* kernel, the following happens: - During boot, some initial messages appear, then the screen flickers a couple of times and it goes blank - I blind-enter the LUKS password, and it appears to work because - pressing the sleep key of the keyboard (laptop) works and the laptop suspends - after waking it up, it works normally This happens with the normal boot options and without options "rhgb" and "quiet". The problem goes away when using the "nomodeset" option in the kernel. Hardware: Dell Precision 7530 laptop, Radeon Pro WX 4150 and integrated GPU Intel UHD Graphics 630. I have tried this with fedora kernels (the distro I use), and also with an OpenSUSE live USB with a kernel 5.8.10. The problem persists, and the "fix" is the same. I attach the kernel log of a boot with the 5.8.11 kernel. Extra information: I have had some problems with suspend, after suspending the screen is blank and I have to close the lid and open again. This happens since various kernels ago, but I never reported because it wasn't serious and I use hibernate anyway. It may be related, since it works after suspend-wake up.
Created attachment 292701 [details] boot log 5.7.17 fedora - working This is the boot log of a boot with the kernel 5.7.17 with fedora, which doesn't present this problem.
Can you bisect?
(In reply to Alex Deucher from comment #2) > Can you bisect? I never did it but I'm happy to help. It will take a while for me to do it, though. Any guidance would be appreciated. I assume that I will start with the first vanilla version that presented this problem, right?
yeah, if it was working with 5.7.0 and not working with 5.8.0, you can just do a bit bisect on https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ between the v5.7 and v5.8 tags. Google for "kernel git bisect howto".
Created attachment 292745 [details] bad-commit I finally get to do the bisect. I attach the result of the guilty commit. I wrongly assumed that it was a problem of amdgpu, but apparently is related to the intel i915 drivers. I guess I should move this bug to the proper place.
Please change the component to Video(DRI - Intel)