On Mon, 18 Jul 2022 08:45:07 -0500
Justin Forbes <jforbes(a)redhat.com> wrote:
There were unfortunately some corner cases with retbleed mitigation
that simply did not work. Most of those should have been worked out
over the past week, but due to the way the embargo was done, there was
a whole lot of testing that just couldn't happen before the code was
merged. As this is your rebuild, the first thing I would do is see if
the proper fedora build boots on this system, and I would not work
with anything pre rc7 at this point. Doing so ensures that you are
missing valid fixes. If the fedora build boots and your build does
not, that is an interesting case to investigate. If the fedora build
does not, that should be filed as a bug and figured out as 5.19 will
be the F37 kernel.
The issue started with the rc5 kernels. I installed and tried to boot
the stock fedora 5.19 fc6 kernel, and it also failed, but fortunately it
panicked and wrote messages to the console. The error is strange. All
of the following was on one line, wrapped here
/init error while loading shared libraries
libsystemd-core-251-3-1.fc37.so cannot open shared object file:
no such file or directory.
But I have systemd-251.3-1.fc37.x86_64 installed, and the file
/usr/lib/systemd/libsystemd-core-251.3-1.fc37.so
exists.
Found the problem. There is a mismatch in the file name.
The kernel should be looking for
/usr/lib/systemd/libsystemd-core-251.3-1.fc37.so
not
/usr/lib/systemd/libsystemd-core-251-3-1.fc37.so
Note the dash instead of a period in front of the 3 in the library
name the kernel is searching for. Typo!
Resolving this will probably resolve all my issues.