Re: The 5.14 kernel in rawhide seems to be unstable, having lockups and failed boots, didn't occur with 5.13
On Sun, 11 Jul 2021 06:22:51 -0700
stan via test <test(a)lists.fedoraproject.org> wrote:
I normally run custom compiled rawhide kernels tuned to my hardware.
In those I turn debugging off. I haven't been able to build one for
5.14 yet because of a problem in the build process. I will try again
with the 20210709 kernel because it seems the fix for the error is in
that package.
I was able to compile a custom kernel with the 20200709 kernel src.rpm
package. So the perf fix is working; the link that used to cause an
error now causes a warning,
warning: absolute symlink:
/lib/modules/5.14.0-0.rc0.20210709gitf55966571d5e.14.20210711.fc35.x86_64/build ->
/usr/src/kernels/5.14.0-0.rc0.20210709gitf55966571d5e.14.20210711.fc35.x86_64
Unfortunately, it doesn't boot correctly because it fails to get the
edid from the monitor. The rest of boot goes off without a hitch, I
can login (without seeing anything) and run commands. When I get to X,
it is in some sort of vga mode with large text and flaky colors and it
is very fragile and hangs after a short time. But I can switch from
there to a virtual console, login as root, and shutdown normally.
The Fedora rawhide kernels do not have this issue. I can see them
probe the EDID in the messages, whereas the custom kernel doesn't. The
custom kernel built with this config file had no problem booting into
this same hardware configuration with a 5.10 kernel, so something has
changed in the settings for getting edid between then and 5.14.
Anyone have a suggestion for where the problem might be?