I upgraded this morning and rebooted. I experienced black screen at login - I was able to switch to a terminal and reboot. After rebooting, and after successfully logging in the system completely froze - magic SysRq didn't work so I had to do a hard power cycle. I have reverted to the previous kernel.
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
I got thrown into rescue maintenance mode when I booted. I looked at the journal and it reported errors about ostree, which was odd since I'm not running silverblue, I'm using normal workstation. I backed out to the previous kernel and all is working fine now. Unfortunately it appears that journal wasn't saved so I can't post any of the error messages. If I'm missing something on how to retrieve messages from that log, please advise, but it appears it wasn't retained.
Just another note, looking at the other negative karma and the thing everyone has in common is that the are using AMD (including myself), so possibly this update is toxic to AMD.
Just another note, looking at the other negative karma and the thing everyone has in common is that the are using AMD (including myself), so possibly this update is toxic to AMD.
./runtests.sh PASS with the kernel-6.3.9-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.
Jun 24 13:18:83 charon Bystemet 11535]: Failed to switch root: Specified switch root path /sysroot' does not seem to be an OS tree. os-release file is missing. Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE
Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Failed with result 'exit-code". Jun 24 13:18:83 charon systemd[1]: Failed to start initrd-switch-root.service Switch Boot. Jun 24 13:18:83 charon systemd[1]: Startup finished in 236us (firmare) 129us (loader) 2.538s (kernel) 8 (initrd) 6.861s (userspace) = 9.3928.
Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Triggering OnFailure dependencies. Jun 24 13:18:83 charon systemd[1]: Started emergency.service- Emergency Shell.
9.371419) charon systemd[1]: Starting initrd-switch-root.service L 9.3771621 charon Bystemet1(535): Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree, os-release file is missing. L 9.3778141 charon systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE
I
L 9.377965] charon systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. L 9.3883871 charon systemd[1]: Failed to start initrd-switch-root.service- Switch Root.
I 9.184595] charon systemd[1]: Reached target emergency.target Emergency Mode. I 9.4284331 charon systemd[1]: Received SIGRIMIN-21 from PID 451 (plymouthd). 9.4384651 charon systemd[1]: Received SIGRTMIM+21 from PID 451 (plymouthd).
Please reconsider pushing this to stable. Multiple people above including myself experience crashes. Sometimes it happens immediately, sometimes after tens of minutes.
6.3.8 seems stable here. I don't know what changed in 6.3.9. I have a similar crash with 6.4.0 in amdgpu so I wonder if it is related.
<knurd> dustymabe: FWIW, the backport (and a few important amdgpu fixes) is already in 6.3.10-rc1, final expected on Wed or Thu
I'm hoping 6.3.10 coming this week has relevant fixes. "amdgpu" is mentioned here. I would test it but I can't find the git repo for 6.3.10-rc1.
A colleague of mine experienced crashes with 6.3.9 on a Ryzen 7 Pro 5850U on Arch Linux. He opened this issue which I think concerns some comments here as well. There should be a fix coming with 6.5-rc1
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 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Working fine here.
Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM.
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
Default and performance pass. HP 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD 630].
kernel test suite PASS
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.
i7-9700K(UHD Graphics 630): kernel regression test passed. Works fine for daily use.
Right after reboot.
I upgraded this morning and rebooted. I experienced black screen at login - I was able to switch to a terminal and reboot. After rebooting, and after successfully logging in the system completely froze - magic SysRq didn't work so I had to do a hard power cycle. I have reverted to the previous kernel.
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
J.K.
Hm, while my dmesg is clean on start, I've got following on sleep today:
Neutral karma to document #2216972 related to my previous comment.
Works great on Lenovo T480! LGTM! =)
Also seeing a hard lockup, so had top revert back to 6.3.8
Ryzen5 5600g/AMDGPU 400 Series Chipset.
I got thrown into rescue maintenance mode when I booted. I looked at the journal and it reported errors about ostree, which was odd since I'm not running silverblue, I'm using normal workstation. I backed out to the previous kernel and all is working fine now. Unfortunately it appears that journal wasn't saved so I can't post any of the error messages. If I'm missing something on how to retrieve messages from that log, please advise, but it appears it wasn't retained.
Just another note, looking at the other negative karma and the thing everyone has in common is that the are using AMD (including myself), so possibly this update is toxic to AMD.
Just another note, looking at the other negative karma and the thing everyone has in common is that the are using AMD (including myself), so possibly this update is toxic to AMD.
Experienced several crashes and deadlocks with 6.3.9. 6.3.8 seems stable.
AMD Ryzen 7 PRO 5850U
Works for me.
./runtests.shPASS with the kernel-6.3.9-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.
BZ#2213462 and BZ#2216459 not tested.
I took a photo of the errors, here they are:
Jun 24 13:18:83 charon Bystemet 11535]: Failed to switch root: Specified switch root path /sysroot' does not seem to be an OS tree. os-release file is missing. Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE
Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Failed with result 'exit-code". Jun 24 13:18:83 charon systemd[1]: Failed to start initrd-switch-root.service Switch Boot. Jun 24 13:18:83 charon systemd[1]: Startup finished in 236us (firmare) 129us (loader) 2.538s (kernel) 8 (initrd) 6.861s (userspace) = 9.3928.
Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Triggering OnFailure dependencies. Jun 24 13:18:83 charon systemd[1]: Started emergency.service- Emergency Shell.
Jun 24 13:18:83 charon systemd[1]: Reached target emergency.target - Emergency Mode.
9.371419) charon systemd[1]: Starting initrd-switch-root.service L 9.3771621 charon Bystemet1(535): Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree, os-release file is missing. L 9.3778141 charon systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE
I
L 9.377965] charon systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. L 9.3883871 charon systemd[1]: Failed to start initrd-switch-root.service- Switch Root.
9.3922131 charon systemd[1]: Startup finished in 236us (firmare) 129us (loader) 2.538s (kernel) 8 (initrd) + 6.861s (userspace) = 9.392s. 9.3923861 charon systemd[1]: initrd-switch-root.service: Triggering OnFailure dependencies. I 9.1843781 charon systemd[1]: Started emergency.service- Emergency Shell.
I 9.184595] charon systemd[1]: Reached target emergency.target Emergency Mode. I 9.4284331 charon systemd[1]: Received SIGRIMIN-21 from PID 451 (plymouthd). 9.4384651 charon systemd[1]: Received SIGRTMIM+21 from PID 451 (plymouthd).
no regressions noted
My problem was related to a grub.cfg cmdline changing karma.
Works on my 3 machines with Ryzen 3 3200G, Core i3-6006U and Core i5-750 & Radeon HD6450. Default and Performance regression tests passed.
Seems OK on my hardware. Ryzen 3700x, Rog Strix B550-F, nvidia from rpmfusion.
Works fine on my Thinkpad Edge (2013)
seems to work fine on a Thinkpad P1 gen3
The rmnet driver is still missing from this kernel.
If i understood correctly the rmnet driver was supposed to be added in this version: https://bugzilla.redhat.com/show_bug.cgi?id=2216459
This update has been submitted for stable by acaringi.
Please reconsider pushing this to stable. Multiple people above including myself experience crashes. Sometimes it happens immediately, sometimes after tens of minutes.
6.3.8 seems stable here. I don't know what changed in 6.3.9. I have a similar crash with 6.4.0 in amdgpu so I wonder if it is related.
I'm hoping 6.3.10 coming this week has relevant fixes. "amdgpu" is mentioned here. I would test it but I can't find the git repo for 6.3.10-rc1.
This update has been unpushed.
A colleague of mine experienced crashes with 6.3.9 on a Ryzen 7 Pro 5850U on Arch Linux. He opened this issue which I think concerns some comments here as well. There should be a fix coming with 6.5-rc1
I assume the fix will be applied to 6.3.10?
It seems not, I still get a hard lockup with 6.3.10 and have to force shutdown, something I do not want to keep doing... Back to 6.3.8