The 6.3.5 stable kernel update contains 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-8b9a1ff294Please login to add feedback.
| 0 | 13 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
./runtests.shPASS with the kernel-6.3.5-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.
BZ#2193110 was not yet tested (VMs seem not affected by the bug, even with cpu-passthrough).
This update's test gating status has been changed to 'passed'.
Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (530.41.03) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).
Works for me, the enabled Default and Performance tests pass OK.
Work Station > Ryzen5 5600g/AMDGPU 400 Series Chipset. (UEFI + Secure Boot). SSD's > RAID1 (ext4) , running Plasma DE from Zawertun's COPR.
Looks good on Ryzen + RX7900 XTX platform.
This warning during the upgrade though:
default test suite PASS
BZ#2193110 does still appear on AMD Ryzen 6850 PRO.
The journalctl is comparable to an earlier one (it is one of the less detailed); the last few minutes are:
Beyond that, I was working with the 6.3.5 kernel around 2 hours without issues with several applications (Fedora 38 KDE Spin).
Given the clear indication of the log of 28th May (regarding
drivers/gpu/drm/ttm/ttm_bo.c), I opened https://lore.kernel.org/dri-devel/69d51cd5-732f-9dc5-4e12-d68990132c85@my.mail.de/T/#uThis update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
Just a small addition to the above +1. Had a couple of hangs on one of my pieces of hardware (no-name fanless PC). The hardware is in a pretty bad state, so it could be that or it could be this particular kernel version. Did have some hangs on this hardware with previous kernels as well, so let's hope it is bad hardware. There are no traces anywhere, so I'll leave my +1 there for now, given this kernel works OK on Lenovo ThinkPad T450s.
Definitely worse on this hardware than 6.3.4-201. I hangs within a minute of booting up. Unfortunately, there are no diagnostics shown as to why the hangs are happening. Everything just locks up.
Working OK so far as a VirtualBox VM and on native h/w.
Dell Precision T5610 2 x Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (8 cores total) NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
Oh, dear. Now it works on that same hardware, no lockups. So, maybe it was just unlucky bad hardware moments before - no idea. Giving +1 again based on my 450s working and ignoring the second machine, unless someone else bumps into similar lockups.
Default & performance tests pass (KVM)
Works for me.
@py0xc3 This is clearly not a new regression in 6.3.5 compared to the current kernel in updates. By continuing to give negative karma to each update when there is not a NEW regression, you are saying that no one else should be able to get their bugs fixed until your bug is fixed.
Works
Works here: Framework laptop, Tiger Lake i5-1135G (Iris Xe Graphics)
works great on Thinkpad T14s Gen 2 AMD
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 OK for me. Ryzen 3700x, Rog Strix B550-F, nvidia from rpmfusion. Both tests passed.
@jforbes sorry, that was not my intention. I wasn't aware that negative karma is only intended for regressions that have not been reported before. In that case, the karma is positive for 6.3.5.
Works great! LGTM! =)
This update's test gating status has been changed to 'failed'.
Default and performance pass. HP 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD 630].
Seems like gating is failing due failing test. We need to bypass or fix this before it's promoted to stage.
This update's test gating status has been changed to 'passed'.
no issues on Thinkpad P1 gen3
Works Fine!
Works Fine!
Works Fine!
no regressions noted
Works fine on my Thinkpad Edge from 2013
This seems to work on my computer.
At least it fixes the issue I had with 6.3.4 (booting, CPU goes crazy and GPU goes to do nothing which result to a black screen (Got an i7-12700k + radeon 7600 )
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
Hardware:
Everything is working fine..
According to
slub_debug=F-enabled logs (see [1] [2] below), there is at least one bug in ath11k:...
AFTER the above:
cat /proc/sys/kernel/tainted= 32. Normally:cat /proc/sys/kernel/tainted= 0.[1] full logs of the above: https://gitlab.com/py0xc31/public-tmp-storage/-/blob/main/slub_debug-F/HIT/slub_debug_HIT.log
[2] related bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2193110
Given the different behaviors of the "occurrences" on my system, it remains unclear if this bug is the only one. I will keep logging.
Seems to work fine on bare-metal HP EliteBook 840 G6 with UEFI and SecureBoot. No issues to report so far and kernel regression tests both PASS.
Seems builds have finished on Koji for 6.3.6. Could we please submit those here?
System doesn't start with kernel over 6.2.15-300.fc38.x86_64
Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-12500H Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop S5602ZA_S5602ZA System Version: 1.0