Looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). Regression test passed (paxtest, selinux-dac-controls and libhugetlbfs skipped).
Works for me, 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-server, nVidia GTX 650 (GK107) nVidia RPM's from RPMFusion (465.31)
Works fine on Acer Aspire V3-571 v: V2.11 CPU: Quad Core Intel Core i7-3632QM GPU: Intel 3rd Gen Core processor Graphics Controller KDE Plasma. No regressions found
Same issue as @ykaul , @tknot and @gtwilliamsbut works otherwise if one removes the suspend= kernel argument.
This issue is not new in this build. Also present in at least 15.12.12 (current stable release). Not even sure it is a kernel issue, may just as well be a dracut issue in how it handles the suspend option.
Kernel passed default kernel test and Selinux test. The output of performance test was not displayed in terminal, instead the config file was opened again by performance test.
Test bench is virtualised fedora workstation running in gnome box with allocated 20gib hdd and 2.5gib ram.
Host OS is Fedora workstation running on 10th gen intel i3 processor, 8gib ram and 1TB hdd(HP 240 G8 laptop).
For those of you seeing boot issues with this kernel, can you please make sure you have either dracut 0.53 or 0.55-2 installed and regenerate the initramfs? It seems that 0.54 broke a lot of systems, and 0.55-2 fixed (some of) them. If you fail with 0.55-2 try 0.53 and report back. I certainly do not want to send out a kernel which breaks boot on a number of systems, but I think in this case, the kernel isn't actually the problem. I would like to verify.
@jfobes I tried to regenerate the initramfs with dracut-055-2 but I was not succeed. So I downgraded dracut to version 053-4 after that I have no boot issue with "Reached target Initrd Root Device" on my Thinkpad X230. I think it is a dracut issue.
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'.
Looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). Regression test passed (paxtest, selinux-dac-controls and libhugetlbfs skipped).
This update's test gating status has been changed to 'passed'.
Default & performance tests pass (KVM)
Default & performance regression tests PASS, libhugetlbfs & paxtest was skipped. Tested on x86_64, PRIME Z270-A, i5-7600K, 16GB DDR4, AMD RX 580 8GB (MESA 21.1.3-1) & 970 EVO M.2.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works for me, 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-server, nVidia GTX 650 (GK107) nVidia RPM's from RPMFusion (465.31)
Works fine for IoT on x86/aarch64/armv7
Work. Intel i5-6500 with nvidia gtx 1060
Works fine on Acer Aspire V3-571 v: V2.11 CPU: Quad Core Intel Core i7-3632QM GPU: Intel 3rd Gen Core processor Graphics Controller KDE Plasma. No regressions found
Boot hangs at "Reached target Initrd Root Device.
Additional info: Intel(R) Core(TM) i7-8550U CPU, Dell XPS 13. Falling back to 5.12.12-300.fc34.x86_64 boots fine.
boots
Slow boot and hangs at "Reached target Initrd Root Device" on two laptops (Thinkpad T490/X230).
Boot hangs at "Reached target Initrd Root Device - X1 gen 6 laptop.
Same issue as @ykaul , @tknot and @gtwilliamsbut works otherwise if one removes the suspend= kernel argument.
This issue is not new in this build. Also present in at least 15.12.12 (current stable release). Not even sure it is a kernel issue, may just as well be a dracut issue in how it handles the suspend option.
Issue filed as https://bugzilla.redhat.com/show_bug.cgi?id=1976621
Karma+ as it's not worse than current stable release.
system boots without issue NVIDIA Corporation GP108 [GeForce GT 1030], AMD Ryzen 7 5800X. Regression passed with performance/default test cases.
Thinkpad T14 laptop failed to boot with same error "Reached target Initrd Root Device". booted with kernel-5.12.12-300.fc34
Booted successfully on Thinkpad T14s with AMD cpu.
Kernel passed default kernel test and Selinux test. The output of performance test was not displayed in terminal, instead the config file was opened again by performance test.
Test bench is virtualised fedora workstation running in gnome box with allocated 20gib hdd and 2.5gib ram. Host OS is Fedora workstation running on 10th gen intel i3 processor, 8gib ram and 1TB hdd(HP 240 G8 laptop).
For those of you seeing boot issues with this kernel, can you please make sure you have either dracut 0.53 or 0.55-2 installed and regenerate the initramfs? It seems that 0.54 broke a lot of systems, and 0.55-2 fixed (some of) them. If you fail with 0.55-2 try 0.53 and report back. I certainly do not want to send out a kernel which breaks boot on a number of systems, but I think in this case, the kernel isn't actually the problem. I would like to verify.
@jfobes I tried to regenerate the initramfs with dracut-055-2 but I was not succeed. So I downgraded dracut to version 053-4 after that I have no boot issue with "Reached target Initrd Root Device" on my Thinkpad X230. I think it is a dracut issue.
cachedrop test fails on my Dell Inspiron 3180 11", all other tests pass, kernel functions fine as a daily driver
This update has been submitted for stable by jforbes.
@jforbes this update will cause some more laptops to break with long boot delay even if it's not really a kernel issue but a dracut issue.
Known workaround for the dracut issue is to regenerate the initramfs without dbus.
dracut -o "dbus" -f
or do downgrade dracut to 053-4 and regenerate the initramfs.
Quite a few people report 5.12.13 completly breaks power management for AMDGPUs.
1) https://gitlab.freedesktop.org/drm/amd/-/issues/1632 2) https://www.reddit.com/r/archlinux/comments/o7x5j8/psa_avoid_kernel_5121351046513rc7_if_using_amd/
Alex Deucher from AMD has confirmed the above issue for 5.12.13. The bug has been fixed in 5.13 and fix is submitted for stable.
This update has been pushed to stable.