The 5.7.10 stable kernel update contains a number of important fixes across the tree.
sudo dnf upgrade --advisory=FEDORA-2020-c0746c5cb5
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
Works fine for me...
The enabled Default and the Performance tests pass OK. AMD 965, x86_64 work station, SSD's > RAID1. Plasma DE, X-server, nVidia GTX 650 (GK107) + nVidia RPM's from Negativo17 (450.57)
Default test: PASS
Performance test: PASS
No new errors or warnings in dmesg.
Model: Dell Latitude 7490
CPU: Intel i7-8650U, GPU: UHD 620, Memory: 16GB, Storage: Samsung 970 EVO, Network: Intel 8265, Intel I219-LM
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Looks good on Lenovo P1gen2
No regressions spotted on Skylake and IvyBridge/7670m laptops
It's ok for me.
Laptop and desktop running fine.
Raspberry pi 3b+ work fine here too
Looks ok for me. Works on baremetal (non UEFI) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver from rpmfusion.org (GTX980 card), VirtualBox 6.1.12 from Oracle and Gnome-Desktop. Regression test passed (paxtest, selinux-dac-controls and libhugetlbfs skipped).
Default & performance regression tests PASS, "libhugetlbfs" & "paxtest" was skipped. Tested on Fedora 32 Workstation (x86_64), PRIME Z270-A, i5-7600K, 16GB DDR4, RX 580 8GB (MESA 20.1.4) & 970 EVO M.2.
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Had an issue since kernel 5.7.7-200.fc32.x86_64, 5.7.8 and 5.7.9 get stuck on searching for 'paths' during boot just after 'plymouth'.
My hardware is a ryzen 3400g. I'm afraid to update at this point to test if this one works, because if it doesn't I'll lose my stable kernel. :(
How should I approach this?
Looking into it more, it looks like the problem is my nvme storage. Something changed in 5.7.8 that is making my nvme drive no longer mount.
[ 3.038736] nvme nvme0: pci function 0000:01:00.0
[ 3.044581] nvme nvme0: missing or invalid SUBNQN field.
[ 3.062966] nvme nvme0: allocated 64 MiB host memory buffer.
[ 3.094878] nvme nvme0: 15/0/0 default/read/poll queues
[ 3.103126] nvme nvme0: Identify Descriptors failed (2)
[ 3.105075] nvme nvme0: Identify Descriptors failed (2)
The missing file descriptor is present in both booting (5.7.7) and not booting kernels. But the difference is, immediately after, I can see the volumes get mounted in /dev. In the non booting kernels it stays simply as /dev/nvme0.
So all I can confirm is that for some reason as of 5.7.7 my nvme is not mounting anymore.
I've regenerated with grub2-mkconfig -o /boot/efa/EFI/fedora/grub.cfg and still not able to boot these newer kernels.
Turns out I am suffering from this regression: https://bugzilla.kernel.org/show_bug.cgi?id=208583
I'm super unlucky to have bought this exact SSD.
Regression since 5.7.9: I can no longer see analog outputs (output-analog* profiles in pactl list are missing) for the built-in Intel HDA:
00:1b.0 Audio device : Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:d751]
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at f7f30000 (64-bit, non-prefetchable) [size=16K]
Capabilities:  Power Management version 2
Capabilities:  MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities:  Express Root Complex Integrated Endpoint, MSI 00
Capabilities:  Virtual Channel
Capabilities:  Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
I'll open a separate bug.
Or, actually, scratch that. I can't reproduce it after a couple of reboots between 5.7.9 and 5.7.10 to collect logs.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.