The 5.14.7 stable kernel update contains a number of important fixes across the tree.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-ab2ecc91bdPlease login to add feedback.
| 0 | 6 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
Default & performance tests pass (KVM)
Works for me: desktop 16GB Intel i7-3770 CPU & laptop 8GB Intel i5-2520M CPU Lenovo T420 (the desktop ran the performance test in 10m9s -- but the laptop took 9m33s, about 10 times longer) - all using the Mate Desktop Environment.
[[[ In kernel-5.14.6-300.fc35 the laptop was 10 times slower than the desktop! ]]]
This update has been submitted for stable by bodhi.
This update's test gating status has been changed to 'passed'.
Kvm tested
kernel regression and performance test PASS ok
This update has been pushed to stable.
wfm
System freezes after few hours. No problem with the kernel-5.14.6-300.fc35.x86_64 and previous versions. Same freeze with F34 https://bodhi.fedoraproject.org/updates/FEDORA-2021-2323f998a6#comment-2222471 . Regression seems to be introduce with 5.14.7 kernels.
Same problem with kernel-5.14.8-300.fc35.x86_64.
cat /sys/block/*/queue/scheduler
mq-deadline kyber [bfq] none mq-deadline kyber [bfq] none mq-deadline kyber [bfq] none mq-deadline kyber [bfq] none mq-deadline kyber [bfq] none mq-deadline kyber [bfq] none none
If after starting kernel-5.14.8-300.fc35.x86_64 I apply the command below then I have no more gel, it seems OK for moment.
echo mq-deadline | tee /sys/block/*/queue/scheduler
cat /sys/block/*/queue/scheduler
[mq-deadline] kyber bfq none [mq-deadline] kyber bfq none [mq-deadline] kyber bfq none [mq-deadline] kyber bfq none [mq-deadline] kyber bfq none [mq-deadline] kyber bfq none none
Sorry it’s my fault, I confused the -200 and -300 versions of kernel 5.14.8 when I downloaded the packages.
It seems to be fine with special 5.14.8-200.fc34.x86_64 from jforbes. Scheduler is [bfq]. 5 hours uptime without freeze.
I know I already test it and run it for a while, but today I experienced a crash when a KVM guest was running on my Aspire V3-571 V2.11 Intel i7-3632QM (8) @ 3.200GHz. It was running fine for more than three hours, before I started the VM and then, after some 20 minutes testing something on the guest machine the host OS hard locks up requiring me to hold the power button down. I can't get anything from dmesg, or from journalctl. I don't have secure boot enabled: mokutil --sb-state =>SecureBoot disabled
Sorry, the problem I found was on kernel 5.14.8-300.fc35.x86_64
The system freezes in my setup i7-4790k with 8GBytes of RAM using the testing repo