I’m really starting to think this issue DOES have something to do with underlying issue that resulted in QSB-098 and it’s possible the fix is not being applied correctly to all machines. In that thread there is also another user who shows no evidence on microcode in his xl dmesg…
I did try just now to regenerate Dracut but no success.
brendanhoar
21d
Is there an order of operations necessary to be sure microcode is loaded after this fix was deployed?
On a fresh R4.2, I have installed kernel-latest (6.6.2-1) and dracut 059-5.fc37, but I think I installed kernel latest before performing the update on dom0 that brought in the new dracut version.
I do not see any evidence of microcode loading in xl dmesg or linux dmesg/linux journalctl output.
--
apparatus
21d
I don’t know how to check it but you can regenerate initramfs just in case:
sudo dracut --regenerate-all --force