The 4.14.8 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-2017-1ebb87e7c0Please log in to add feedback.
| 0 | 5 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
LGTM; X260
This update has been pushed to testing.
wfm: desktop 16GB Intel i7-3770 CPU, laptop 16GB Intel i7-3610QM CPU, laptop 8GB Intel i5-2520M CPU Lenovo T420 (very slow, took almost 2 hours for performance tests!), - all using the Mate Desktop Environment
x86_64, ARMv7
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
Works for me.. Regression tests pass OK.
x86_64 work station, Plasma DE, X-server, nVidia card GTX 650 (GK107) /nouveau
works for me
works for me
Works great on Lenovo X220! LGTM! =)
works for me on desktop Intel i5-3470 CPU, laptop Intel i5-2520M Lenovo T420
Looks good to promote ;)
Works for me on Thinkpad X250
Regressions passed
wfm -- tests pass
No regressions noticed.
No regressions noted.
This update has been submitted for batched by jforbes.
This update has been submitted for stable by jforbes.
This update has been pushed to stable.
With this version the GUID mapping of my nfs4/kerberos file system does not work any more. reverting 4.14.7 fix the issue.
karma: -1
I got a big issue with this kernel. I cannot boot with it (it goes directly in emergency mode): - there is some error with nvme module on boot Some volume are in error (even the /boot/efi one !! ) - The main error is "systemd-modules-load[515]: Failed to find module 'ecryptfs'" but the file is really in /lib/modules/4.14.8-300.fc27.x86_64/kernel/fs/ecryptfs
reverting to 4.14.7 fix my issue...
from previous post... I reset the setup (reinstall kernel*) and now it seems ok ... I don't know what was wrong...