On Sun, 26 Jul 2020 at 12:47, Sreyan Chakravarty <sreyan32@xxxxxxxxx> wrote:
I just upgraded to the new 5.7 kernel and it has a lot of bugs.
If you are using ext4, look for the "swapfile has holes" message. There is a kernel bug, but two proposed fixes, one looks like a quick hack, the other points to a more basic flaw in the implementation.
One misconfiguration can cause multiple failures.
Other distros are reporting problems and have workarounds: https://bbs.archlinux.org/viewtopic.php?id=256503
It can't even initialize my swap file:
Jul 26 21:01:12 localhost.HPNotebook systemd[1]: fedora.swap.swap:
Failed with result 'exit-code'.
6 Jul 26 21:01:12 localhost.HPNotebook systemd[1]: Failed to activate
swap /fedora.swap.
7 Jul 26 21:01:12 localhost.HPNotebook systemd[1]: Dependency failed
for Swap.
8 Jul 26 21:01:12 localhost.HPNotebook systemd[1]: swap.target: Job
swap.target/start failed with result 'dependency'.
9 Jul 26 21:01:12 localhost.HPNotebook swapon[994]: swapon:
/fedora.swap: swapon failed: Invalid argument
10 Jul 26 21:01:26 localhost.HPNotebook swapon[1084]: swapon:
/fedora.swap: swapon failed: Invalid argument
11 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: fedora.swap.swap:
Failed with result 'exit-code'.
12 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: Failed to activate
swap /fedora.swap.
13 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: Dependency failed
for Swap.
14 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: swap.target: Job
swap.target/start failed with result 'dependency'.
15 Jul 26 21:01:26 localhost.HPNotebook swapon[1093]: swapon:
/fedora.swap: swapon failed: Invalid argument
16 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: fedora.swap.swap:
Failed with result 'exit-code'.
17 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: Failed to activate
swap /fedora.swap.
18 Jul 26 21:01:26 localhost.HPNotebook systemd[1]: Dependency failed
for Swap.
This doesn't happen in 5.6
There are a slew of other problems.
A log file can be found here:
https://pastebin.com/iL9Yd5cj
I really am too tired to file a bug since nothing really gets fixed.
Maybe you shouldn't be using Fedora. One reason Fedora exists is to catch problems like this. Given that there is a simple workaround and more than one way to "fix" it, it may take some time for a fix to make it into the kernel.
The bug was reported in May, so "some time" might translate to "real soon now".
What I want to do is uninstall the 5.7 kernel. apply
Why not apply the workaround.
If I uninstall the kernel will running an older kernel cause problems
during system upgrade ?
--
Regards,
Sreyan
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
George N. White III
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
