The 6.14-rc6 update contains a number of important fixes across the tree.
The 6.14-rc5 kernel update contains a number of important fixes across the tree.
The 6.14-rc4 kernel build contains a number of important updates 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-2025-1b8a020e07Please login to add feedback.
| 0 | 5 | 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's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
That looks like this depends on FEDORA-2025-363f87fb8c , so it's probably transient, it should no longer be a problem once we've done a compose with that update in it.
Looks good here as a VirtualBox guest. Tests all passing except the usual timer-overhead (seems usual for VirtualBox).
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
adamwill edited this update.
Curious how it ended up in the build root if it is not in a compose.
default & performance tests pass (KVM)
Things go into the buildroot as soon as they're pushed stable (more or less), but aren't available to users till after the next compose is done and synced.
For openQA tests, I pull in the buildroot repo as a package source when testing Rawhide updates and updates for Branched before updates-testing activation (otherwise this just happens way too often), but for Branched after u-t activation and for stable releases, I intentionally don't include the buildroot repo, to ensure things don't get pushed out of order or anything.
...although, hmm, now I think about it, I'm not sure if that's the correct cutoff. maybe the correct cutoff should be just 'whether updates is a separate repo or not', i.e. include buildroot repo for rawhide and branched always. mmm, lemme think about it.
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
There is an ongoing freeze; this will be pushed to stable after the freeze is over.
This update has obsoleted kernel-6.14.0-0.rc5.43.fc42, and has inherited its bugs and notes.
Following up on my concern from rc5, ntsync driver is still not being built. The config now sets it to CONFIG_NTSYNC=m, but i think it needs to be explictly set to
y.rpm -qlp kernel-modules-core-6.14.0-0.rc6.49.fc42.x86_64.rpm | grep ntsync /lib/modules/6.14.0-0.rc6.49.fc42.x86_64/kernel/drivers/misc/ntsync.ko.xz
Working fine on baremetal
Works
AMD Ryzen 5 both tests are a PASS.
Works great on Lenovo M715q! LGTM! =)
This update has been pushed to stable.
kernel-6.14.0-0.rc6.49.fc42 is booting only when kernel option 'pci=nomsi' is set as a workaround
previous kernels 6.12.*.fc41.x86_64 (e.g. 6.12.15-200.fc41.x86_64) are booting on same system and same HW without this kernel option set
system is current pre-beta "Fedora42" on bare metal