The 5.19.4 kernel rebase contains a number of important bug fixes, new hardware support, and feature enhancements 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-2022-b0205d1c7f
Please login to add feedback.
0 | 11 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
Works on Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000. wi-fi: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1 - Passed kernel regression tests.
This update's test gating status has been changed to 'passed'.
Working OK. As usual timer-overhead often fails in a VirtualBox VM but that seems to be normal these days.
Dell XPS 13 9350 laptop (i7-6560U CPU @ 2.20GHz × 4) and on two NUC6i5SYK (i5-6260U @ 1.80GHz × 4). Both Default and Performance regression tests pass on the laptop and on both NUCs. No problems noticed.
Works for me: all using the Mate Desktop Environment.
sirius: desktop 16GB Intel i7-3770 CPU desktop (SSD + 5 hard drives in RAID-6) real:10m14.311s user:4m37.197s sys:4m39.050s sedna: laptop 8GB Intel i5-2520M CPU Lenovo T420 (SSD only) real:10m16.250s user:4m4.536s sys:4m50.540s
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:20m11.405s user:9m37.763s sys:7m45.899s //////// This used take about 14 minutes!
*** I’m intensely curious as to the reason for why sedna seems to randomly fluctuate between short (normally under 11 minutes) & extremely long (100+ minutes) elapsed times for the performance test!
Tested on Dell Inspiron 14 7425 2-in-1 laptop (AMD Ryzen 7 5825U). This update resolved a bluetooth issue from the previous kernel 5.18 series.
Default & performance tests pass (KVM)
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
https://bugzilla.redhat.com/show_bug.cgi?id=2111555 is still an issue in 5.19.4.
Works for me..
It's been up for a couple of hours now with no issues noticed. The enabled Default and Performance tests pass OK.
https://bugzilla.redhat.com/show_bug.cgi?id=2121844 This started happening for me.
Works for me. Passes regression test.
Unable to start systemd-nspawn machines with LUKS encrypted storage (XFS in my case): #2121883
Starting systemd-nspawn@mymachine.service - Container mymachine... loop0: detected capacity change from 0 to 20975616 loop0: p1 Failed to dissect image '/var/lib/machines/mymachine.raw': Connection timed out systemd-nspawn@mymachine.service: Main process exited, code=exited, status=1/FAILURE systemd-nspawn@mymachine.service: Failed with result 'exit-code'. Failed to start systemd-nspawn@mymachine.service - Container mymachine.
Normally, and in 5.18.x kernels, I would get the prompt to enter the LUKS password to decrypt the volume.
Otherwise the update seems to be generally functional so neutral karma.
WARNING: CPU: 2 PID: 424 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn21/rn_clk_mgr_vbios_smu.c:98 rn_vbios_smu_send_msg_with_param+0xf1/0x100 [amdgpu]
I'm getting an non-reportable error after waking up from sleep on an Lenovo IdeaPad 5 Pro 14ACN6. Where should I report this?
It seems the kernel recovers though and the machine is functional.
https://bugzilla.redhat.com/show_bug.cgi?id=2121844 also affects me
Works for me.
It runs for days now and looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (515.65.01) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
wfm
./default/cachedrop
seems to fail ifthirdparty=y
is enabled with NVIDIA drivers. Neutral karma because it passes in KVM/actual hardware with default settings.Tested on MacBookPro12,1: https://linux-hardware.org/?probe=9e48c5e245
This update has been submitted for stable by jforbes.
https://bugzilla.redhat.com/show_bug.cgi?id=2107838 is still happening
This update has been pushed to stable.
Some Arch users also have the battery state bug and they have some finding. Hope this helps https://bugs.archlinux.org/task/75653 https://bugs.archlinux.org/task/75682 https://bbs.archlinux.org/viewtopic.php?id=278933
I think this is the issue that I talked about when waking the machine from sleep.
https://gitlab.freedesktop.org/drm/amd/-/issues/2110