./runtests.sh PASS with the kernel-6.3.10-200.fc38.x86_64 builds within a kvm/qemu VM (KDE spin, up to date with all testing repos of F38 enabled) with CPU-passthrough on a AMD Ryzen 6850 PRO host. No third party modules (tainted = 0).
I tested the VM some minutes with average activities, works fine so far. No errors/issues when using it.
Occurrence of Fedora BZ#2193110 / kernel BZ#217528 was not yet tested.
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (535.54.03) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
When I've logged into Plasma 5.27.6 on Wayland from sddm after booting 6.3.10, the Plasma splash screen appeared for around a second and then the screen went black indefinitely. This problem happened each time with 6.3.10, but it didn't happen with 6.3.9 or earlier. amdgpu errors and warnings were shown in the journal as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2218414 I bisected the problem to 1ca399f127e0a372537625b1d462ed586f5d9139 "drm/amd/display: Add wrapper to call planes and stream update"
The 6.3.9 problem persists - random lockups, crashes, black screens. Does not respond to SysRq - need to power cycle. Reverted to 6.3.8 which does not suffer from the same problem. Can't see anything unusual in the journals.
Lenovo Legion 5
AMD Ryzen 7 5800H with Radeon Graphics (16) @ 3.200GHz
AMD ATI Radeon Vega Series / Radeon Vega Mobile Series
AMD ATI Radeon RX 6600/6600 XT/6600M
Two similar Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3) kernel 6.3.1-200.fc38.x86_64 (512 GB SSD in one abd 1 TB SSD in the other).
All three systems are running fine. Ran default and performance regression tests on one of the NUCs and both passed.
Exact same issue on my Slimbook - random lockups, crashes, black screens. Does not respond to SysRq - need to power cycle. Reverted to 6.3.8 which does not suffer from the same problem. Can't see anything unusual in the journals.
Slimbook Titan
AMD Ryzen 9 5900HX with Radeon Graphics
Radeon Vega Series / Radeon Vega Mobile Series
GeForce RTX 3070 Mobile / Max-Q
Works fine at first glance with my 3 machines, but similar to previous candidate 6.3.9 the boot process fails now and then on my main machine with Ryzen 3 3200G at varying stages and with various symptoms (systemd messages get stuck, screen becomes black, kernel oops displayed).
If the problem occurs late enough, error messages like "kernel: BUG: kernel NULL pointer dereference, address: 0000000000000010" can be found in the journal. If boot finishes successfully the machine continues to work normally.
Changing my karma, as others have noted, this update has issues with some laptops. After login you get the black screen. This happens on both Gnome and KDE, and whether you are using X11 or Wayland. My laptop uses an AMD A10 processor. Backout to 6.3.8 kernel circumvents issue.
This update has been submitted for testing by acaringi.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Seems fine here.
Intel NUC i7 NUC11PAH 1 x 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
ASUS G750JS 1 x Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) NVIDIA Corporation GK104M [GeForce GTX 870M] (rev a1)
This update has been pushed to testing.
Works.
This update can be pushed to stable now if the maintainer wishes
Works great on Lenovo T480! LGTM! =)
Works on Ryzen 9 7900 + RX 7900 XTX
Works with Ryzen 7600X + RX 6600 XT
LGTM, Lenovo Yoga Slim 7 Pro 14ACH5, CPU AMD Ryzen 9 5900hx, GPU AMD Renoir, Wifi Mediatek mt7921e
Default & performance tests pass (KVM)
Same issue on another Intel NUC running. #2216972
Working fine here.
Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz
Graphics Processor: Mesa DRI Intel® HD Graphics 4000. driver: i915 v: kernel arch: Gen-7
wi-fi: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel.
Default fedora btrfs filesystem.
Suspension works
Passed all kernel regression tests
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
Works for me.
./runtests.sh
PASS with the kernel-6.3.10-200.fc38.x86_64 builds within a kvm/qemu VM (KDE spin, up to date with all testing repos of F38 enabled) with CPU-passthrough on a AMD Ryzen 6850 PRO host. No third party modules (tainted = 0).I tested the VM some minutes with average activities, works fine so far. No errors/issues when using it.
Occurrence of Fedora BZ#2193110 / kernel BZ#217528 was not yet tested.
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (535.54.03) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
kernel test suite PASS
Seems OK on my hardware. Ryzen 3700x, Rog Strix B550-F, nividia from rpmfusion.
Works
When I've logged into Plasma 5.27.6 on Wayland from sddm after booting 6.3.10, the Plasma splash screen appeared for around a second and then the screen went black indefinitely. This problem happened each time with 6.3.10, but it didn't happen with 6.3.9 or earlier. amdgpu errors and warnings were shown in the journal as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2218414 I bisected the problem to 1ca399f127e0a372537625b1d462ed586f5d9139 "drm/amd/display: Add wrapper to call planes and stream update"
The 6.3.9 problem persists - random lockups, crashes, black screens. Does not respond to SysRq - need to power cycle. Reverted to 6.3.8 which does not suffer from the same problem. Can't see anything unusual in the journals.
J.K.
Exactly the same issue for me again as well, so reverted back to using 6.3.8
Desktop box, Ryzen5 5600g/AMDGPU 400 Series Chipset.
Works on my Thinkpad Edge (2013)
Seems to work fine on bare-metal HP Z440, AMD RX570 with UEFI. No issues to report so far and kernel regression tests both PASS.
Works without issues till now
Works without issues till now
Dell XPS 13 9350, Intel Core i7-6560U × 4, Mesa Intel Iris Graphics 540 (SKL GT3) kernel 6.3.1-200.fc38.x86_64
Two similar Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3) kernel 6.3.1-200.fc38.x86_64 (512 GB SSD in one abd 1 TB SSD in the other).
All three systems are running fine. Ran default and performance regression tests on one of the NUCs and both passed.
I have ".1" instead of ".10" twice in my comment immediately above this. Both should be 6.3.10-200.fc38.x86_64
Exact same issue on my Slimbook - random lockups, crashes, black screens. Does not respond to SysRq - need to power cycle. Reverted to 6.3.8 which does not suffer from the same problem. Can't see anything unusual in the journals.
Slimbook Titan AMD Ryzen 9 5900HX with Radeon Graphics Radeon Vega Series / Radeon Vega Mobile Series GeForce RTX 3070 Mobile / Max-Q
J.K.
Works fine at first glance with my 3 machines, but similar to previous candidate 6.3.9 the boot process fails now and then on my main machine with Ryzen 3 3200G at varying stages and with various symptoms (systemd messages get stuck, screen becomes black, kernel oops displayed).
If the problem occurs late enough, error messages like "kernel: BUG: kernel NULL pointer dereference, address: 0000000000000010" can be found in the journal. If boot finishes successfully the machine continues to work normally.
Changing my karma, as others have noted, this update has issues with some laptops. After login you get the black screen. This happens on both Gnome and KDE, and whether you are using X11 or Wayland. My laptop uses an AMD A10 processor. Backout to 6.3.8 kernel circumvents issue.
This update has been obsoleted by kernel-6.3.11-200.fc38.
See Fedora BZ#2218590, which started with 6.3.8 but remains on 6.3.10 (I now updated to 6.3.11):
...
...