The 5.14.12 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-38f956578e
Please login to add feedback.
0 | 4 | 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'.
Default & performance tests pass (KVM)
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
Works for me, it's been up for quite a few hours now with no issues noticed.
The enabled Default and Performance tests pass OK. AMD 965, x86_64 work station, SSD's > RAID1. Plasma DE from Zawertun's COPR, X-org, nVidia GT 1030 using nVidia RPM's from RPMFusion (470.74)
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Desktop 16GB Intel i7-3770 CPU & laptop 8GB Intel i5-2520M CPU Lenovo T420 (the desktop ran the performance test in 10m03s -- but the laptop took 106m24s, about 10 times longer) - all using the Mate Desktop Environment. Other than the slowness, the regression tests both passed.
@jforbes The laptop should not be taking more than 10 times the elapsed time of the desktop to do the performance test, as on last kernel 5.14.11 version the laptop was actually slightly quicker by a few seconds!
works
@nivag This is why I have never recommended most users run the performance testing. What else was your laptop doing at the time? What was your desktop doing at the time? Performance testing is only interesting comparing multiple kernels on the same machine under controlled testing environments and multiple runs. That means otherwise idle machine, clean boots in between tests, etc. I would be interested in your running it again though and comparing results with the first run.
Passed the regression tests. Acer Aspire V3-571 v: V2.11 Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000.
Works great on Lenovo T480! LGTM! =)
@jforbes For every kernel I have tested, on both the laptop and the desktop, I have run the tests in near identical conditions as far as is practicable. The machines have all the latest updates applied prior to testing. I have a newer more powerful AMD desktop that I do most of my work on.
The laptop and the desktop are rebooted after installing the new kernel. The System monitor is expanded. LibreOffice is started to display some notes. Palemoon is used to display the bodhi update details. The kernel-tests directory is installed afresh prior to the tests, and deleted afterwards. Both the regression tests are run as root in the order specified. The machines are never rebooted between the tests. No other work is done on the machines while the tests are running, nor between test runs.
Essentially the methodology is the same for all runs of the regression tests on both machines.
I reran just the performance test on the laptop and it ran for ms which is not significantly different to the previous run.
semanage boolean -m --on selinuxuser_execheap
time ./runtests.sh -t performance ; date
Test suite called with performance Using config in CONFIG.sedna Sat 16 Oct 08:52:46 NZDT 2021 Latency measurements Sat 16 Oct 09:02:21 NZDT 2021 Calculating file system latency Sat 16 Oct 09:06:15 NZDT 2021 Local networking Sat 16 Oct 09:10:58 NZDT 2021 Bandwidth measurements Sat 16 Oct 10:22:28 NZDT 2021 Calculating context switch overhead Sat 16 Oct 10:36:22 NZDT 2021 ./performance/lmbench3 PASS
Test suite complete PASS
Your log file is being submitted... Upload successful! The following information is not submitted with your log; it is for informational purposes only. Vulnerability status: /sys/devices/system/cpu/vulnerabilities/itlb_multihit:KVM: Mitigation: VMX unsupported /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion /sys/devices/system/cpu/vulnerabilities/mds:Mitigation: Clear CPU buffers; SMT vulnerable /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl and seccomp /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling /sys/devices/system/cpu/vulnerabilities/srbds:Not affected /sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected
real 103m42.556s user 68m42.265s sys 36m32.128s Sat 2021-10-16 10:36:27 NZDT
semanage boolean -m --off selinuxuser_execheap
Got this right after reboot with this new kernel, but can't report due Vbox modules: https://retrace.fedoraproject.org/faf/reports/247589/
There many
amdgpu
changes in this kernel.Works well on P1 Gen 2
@nivag I read from your previous comments on other kernel release version. If you mean sometime faster and sometime slower on performance test, it's happen also to me. But since the all result is pass, I'm ok with that.
From my understanding it's may be related to any background app or background tasks on the system it's self.
Let's say I have an app that always try to check the network connection and if connected to internet it will find an update (like email etc.), I believe it will impact the performance test.
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
@oprizal The laptop was extremely lightly loaded, It was only running the applications I mentioned above. My email client is on my main desktop. There are no applications that would have changed the elapsed time tenfold for some runs and not others. Also if you have a look at all the time i've recorded, they are all either very close to 10 minutes or 110 minutes. I never saw times between 15 and 105 minutes. So applications should not be blamed for the excessive elapsed time.
The differences in elapsed times are significant, greater than 5 sigma, to use the parlance of the LHC at CERN.
This update has been submitted for stable by jforbes.
No regressions, kernel tests passed
LGTM
works on my Thinkpad T480s
Works fine on some very old hardware
This update has been pushed to stable.