The v4.16.6 update contains important fixes across the tree.
Additionally, 4.16.6-302 includes a fix for a boot hang due to the cryptographic random number generator.
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-2018-cf65b3a7a2Please login to add feedback.
| 0 | 0 | Test Case kernel regression |
This update has been submitted for testing by jcline.
works well. installed from koji.
Works fine here too (Phenom II, RX560).
karma: +1
works for me, x86_64, i3-2350M
This update has been pushed to testing.
Works fine as a ESXi 6.7 VM
Works for me.. Regression tests pass OK.
x86_64 work station, Plasma DE, X-server, nVidia card GTX 650 (GK107) /nouveau
works well on T440s and Intel-based desktop (with GTX750 nouveau). no regression noted. passed default kernel regression test.
WFM. Tested on armv7hl: on Raspberry Pi 3 and on Orange Pi PC
Works
No regressions on T450s, XS35GTv2 and a VM.
Looks fine and ready for stable.
Works great on a Lenovo T480 w/ Nvidia dGPU! LGTM! =)
jcline edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jcline.
works fine for me on i7-5820K. regression tests passed. successfully build an out of tree kernel module.
Fixes the reproducer for the libgcrypt fips rng bug.
Works correctly here on i7-4700HQ.
karma: +1
not showing up in the packages app: https://apps.fedoraproject.org/packages/kernel
I think it needs to be pushed at least to testing in order to show there.
Is "This update has been submitted for testing by jcline" different from pushed to testing? Anyway, I think there is a bug with the package app since it shows an old 4.16.2 kernel, not even 4.16.6.-300
This is what I get from dnf with updates-testing:
Problem: cannot install both kernel-4.16.6-300.fc28.x86_64 and kernel-4.16.6-300.fc28.x86_64 - cannot install the best update candidate for package kernel-4.16.6-300.fc28.x86_64 - cannot install the best update candidate for package kernel-4.16.6-200.fc27.x86_64
That likely means that the mirror you are connecting to does not yet have the packages (still -300, and you can't install the same kernel a second time). You can try..
sudo dnf clean all && sudo dnf --enablerepo=updates-testing update kernel*or just wait a couple of hours.
@augenauf, someone noticed that packages issue yesterday I think and brought it up in the #fedora-admin channel (maybe it was you?). My guess is it missed some messages and doesn't do any polling so it didn't get updated. It looks to be updated now that the package actually got pushed. When updates are submitted for testing, they don't actually end up in the updates-testing repository until release engineering triggers a push (about once a day).
This update has been pushed to testing.
This update has been submitted for batched by jcline.
This update has been submitted for stable by jcline.
wfm - no regression noted.
This update has been pushed to stable.