The 5.6.5 stable kernel rebase contains new features, improved hardware support, and a number of important fixes 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-2023-4c8291ba6aPlease login to add feedback.
| 0 | 10 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted kernel-6.4.16-200.fc38, and has inherited its bugs and notes.
This update's test gating status has been changed to 'failed'.
https://gitlab.freedesktop.org/drm/amd/-/issues/2830 6.5.x including 6.5.4 have this serious amdgpu regression. You can crash it while zooming Google Maps in chromium.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Got this error on one of my machines that had the perf package installed
Oh wait, never mind. I'm dumb. The machine in question is one I'm trying out Fedora 39 on
Apart from #2239331 nothing to report. Thank you for keeping us up to date!
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
https://gitlab.freedesktop.org/drm/amd/-/issues/2830 amdgpu crash regression confirmed across 3+ generations of Ryzen APU's. Please help by bringing this to the attention of AMD.
Works for me, the enabled Default and Performance tests pass OK.
Work Station > Asus Prime mobo, Ryzen5 5600g/AMDGPU 400 Series Chipset, (UEFI + Secure Boot) SSD's > RAID1 (ext4) running Plasma DE from Zawertun's COPR.
Works great on Lenovo T480! LGTM! =)
No issues on desktop amdgpu (RX 7900 XTX), everything works fine, no issues (but not enough testing) on Lenovo P1 gen2 either
default & performance tests pass (KVM)
> https://gitlab.freedesktop.org/drm/amd/-/issues/2830 amdgpu crash regression confirmed across 3+ generations of Ryzen APU's. Please help by bringing this to the attention of AMD.
From the bug report:
These are the most important people for amdgpu development. They are well aware.
Works.
There are linux-firmware updates in updates-testing, including for AMD. Are those relevant?
Finally vibration on Xbox SX controller now works via bluetooth with 6.5 kernel.
Working fine
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 working
Passed all kernel regression tests
Works for me: using the Mate Desktop Environment.
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) (from lscpu: max MHz 4370, min MHz 1400, BogoMIPS 3593) real:17m16.665s user:7m11.804s sys:7m39.856s
amd-gpu-firmware-20230919-1.fc38.noarch then regenerated the initramfs makes no difference.
Tested with both kernel-6.5.4 and kernel-6.5.5rc1.
Ok here. Ryzen 3700x, Rog Strix B550-F, nvidia 2070 from rpmfusion, Intel SSD.
Working for me in 38.
HP 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD 630]
(Still) unusable due to https://bugzilla.redhat.com/show_bug.cgi?id=2239807
Works for me. The bug linked in https://bodhi.fedoraproject.org/updates/FEDORA-2023-4c8291ba6a#comment-3205659 has a comment containing a reproducer on Firefox. I tried it, and couldn't trigger the bug.
I was unable to reproduce the amdgpu crash in Firefox. It crashes consistently with Chrome or Chromium, the latter is available in Fedora.
Note: There is something different about Live USB where it doesn't crash. Ryzen 7 5850U with Fedora 39 Beta Workstation Live does not crash in chromium despite it having the problematic kernel-6.5.2. Unclear why it is different during Live runtime. My guess would be power management being inhibited or something.
Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3)
default and performance tests passed. working fine in normal use
Works without issues till now
Seems to work with my 3 machines with Ryzen 3 3200G, Core i3-6006U and Core i5-750 & Radeon HD 6450 (all with Xfce spin installed). Could not reproduce amdgpu issues with Ryzen 3 3200g, but noticed new prio 3 message "kernel: integrity: Problem loading X.509 certificate -126" in journal of 2 machines.
Works fine, no issues on Lenovo ThinkPad Z16 Gen 1 (AMD Ryzen 7 PRO 6850H + AMD RX 6500)
@norbertj FYI there is a bug report on the X.509 certificate warning
https://bugzilla.redhat.com/show_bug.cgi?id=2239331
jforbes edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
The timer-overhead test is failing in a VirtualBox VM but that's normal. Otherwise it's working OK.
This update's test gating status has been changed to 'passed'.
Up for an hour or so now, no issues noticed. The enabled Default and Performance tests pass OK.
Work Station > Asus Prime mobo, Ryzen5 5600g/AMDGPU 400 Series Chipset, (UEFI + Secure Boot) SSD's > RAID1 (ext4) running Plasma DE from Zawertun's COPR.
6.5.5-200.fc37.x86_64
Works for me: using the Mate Desktop Environment.
mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) (from lscpu: max MHz 4370, min MHz 1400, BogoMIPS 3593) real:17m18.636s user:7m9.388s sys:7m38.049s
no regressions noted
Works good. Ryzen 3700x, Rog Strix B550-F, nvidia 2070 from rpmfusion, Intel SSD. Played Xonotic CTF for a half hour smoothly. Seems OK for emails, etc. Reboots OK.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works smooth, no issues. Lenovo, Ryzen 5800U, WD nvme, MediaTek wifi/bt, no gpu.
kernel-6.5.5 has the same regression as kernel-6.5.[0-5] where amdgpu crashes hard with multiple generations of AMD APU's. I'm investigating further.
default & performance tests pass (KVM) on 6.5.5
Works fine on a AMD Ryzen 7 PRO 6850U host with Fedora 38 KDE. No regression tests done on the host, only in a VM with cpu passthrough for F39 (see FEDORA-2023-0defc5c6ec).
Fixes https://gitlab.freedesktop.org/drm/amd/-/issues/2657
Enables rumble in xbox series controllers connected via bluetooth.
Boots and functions as expected. No regression tests were run.
5600X / RX 6800
Both kernel regression tests passed, but I'm still hitting #2239331, not sure what has changed since 5.4.X, but if it's not a bug (as in: intended), then I apologize for the confusion and will make no further mention of it.
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.
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Update seems to cause standby/serious kernel crashes: https://github.com/fedora-silverblue/issue-tracker/issues/495 https://gitlab.freedesktop.org/drm/amd/-/issues/2830#note_2075926
Likely a kernel regression.
It is known, it is tracked in the upstream bug mentioned here, and in Bug 2240859, where I scratch build with a fix is linked. The fix for at least 2 of them will be in 6.5.6. I am not sure why kernel bugs are being filed in github for silverblue as those aren't looked at by the kernel folks. I don't think there has ever been a kernel bug that only impacts silverblue.
@jforbes I personally filled it because how an I supposed to know our is a kernel bug? I posted it anywhere relevant I thought of where I may get support for my system, which was the silverblue issue tracker and AskFedora, all crosslinked. Also the relevant solution was given me at the first one, so well… I mean it could have been anything, I don't know, I was just seeking support/reporting a very spurious issue.
I suppose I don't know how silverblue communicates the support model there, but I would assume the issue tracker is around the code in those repositories for composing silverblue, etc. Any actual system issues are likely tied to packages installed in silverblue and bugzilla is the place to track them where maintainers are actually paying attention to those bugs. I could be wrong though, I haven't really read the silverblue docs. For future reference though, most things around hardware drivers will fall to kernel. blank screens, suspend/resume issues, etc.
Stuck during boot with RX 5700 XT. Last display message should be:
[drm] fb0: amdgpudrmfb frame buffer deviceAs mentioned by wtogami, the AMDGPU crash seriously affects general system use. For me, it always happens in under 30 minutes of watching full-screen YouTube videos. A full forced shutdown via the power button has to be performed every time this happens (SysRq commands do not work).
My bad; it's not stuck indefinitely. My issue might be related to https://bbs.archlinux.org/viewtopic.php?id=289257
It boots after waiting a while. Cannot comment on
amdgpustability yet.