![](https://popplesburger.hilciferous.nl/pictrs/image/c1ad0046-f2ee-4988-aa2d-533aca036635.jpeg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Unless you have some kind of knockoff SSD, that ūsung SSD
looks like something is corrupted to me. usb 1-10 device descriptor read/64, error -71
might be unrelated.
This could be a problem with RAM defects or overclocking. If your computer is overclocked, try setting it to stock configuration. Also run a memtest to check if your RAM sticks aren’t going bad. I don’t know what might’ve changed between 6.8.9 and 6.8.10 to cause this, but it could just be a coincidence (i.e. the kernel defaulting to a different RAM page that suffers from corruption for whatever reason).
These messages are actually part of the systemd startup sequence, so the kernel has already loaded at this point. This means the problem may not be the kernel, but the initramfs installed/generated for your computer. You can try regenerating your initramfs on Fedora by running dracut --regenerate-all
as root. Before you do that, you may also want to double check your /etc/fstab
to make sure nothing accidentally added a swap device for some reason.
Corporate stuff is probably already running on unsupported and unpatched Linux distros if they still haven’t migrated to Python 3. I doubt the new version of Fedora removing the binaries will make much of a difference.