The 4.14.13 stable kernel update contains a number of important fixes across the tree. This is also the first update to contain some spectre mitigations. Some patches for variant 1 as well as the initial retpoline build for variant 2. These variant 2 mitigations will improve with further patches, and once compiler support is improved.
sudo dnf upgrade --refresh --advisory=FEDORA-2018-21a7ad920c
Please login to add feedback.
0 | 4 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
Updated rpms and rebooted (note I have also new microcode_ctl). I ran also the test suite (both tests pass) and submitted results.
One of the enhancements comparing to -11 is that it now shows details under /proc/cpuinfo in 'bugs' section - in my case: cpu_meltdown spectre_v1 spectre_v2
$ uname -a
Linux unknown 4.14.13-300.fc27.x86_64 #1 SMP Thu Jan 11 04:00:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
jforbes edited this update.
1532058 is fixed, as well as #1497559
karma: +1
Works for me on my Acer Aspire VX 15 / x86_64.
dmesg: has a new initial line:
[ 0.000000] microcode: microcode updated early to revision 0x80, date = 2018-01-04
/proc/cpuinfo diff between 4.14.11 and 4.14.13: Is the cpu MHz difference normal?
Works for me.
Boot tested on x86_64, ppc64le, ppc64le and aarch64 virtual machines. x86_64 indicates minimal ASM retpoline and KPTI are enabled.
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, - all using the Mate Desktop Environment
works fine for me on Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
AMD Athlon(tm) Processor LE-1640:
AMD Athlon(tm) Processor LE-1640:
WFM, Thinkpad X250 (Broadwell)
WFM
@sezeroz: CPU Mhz difference in /proc/cpuinfo is presumably due to this change pulled into 4.14.13:
Further details can be found in the change log: https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.13.
@dhgutteridge: Thanks.
Boots on T450s, XS35GTv2 and a VM.
works for me on two x86_64 boxes.
This update has been submitted for batched by jforbes.
This update has been submitted for stable by jforbes.
Since feedback about AMD processors was requested, here's data from a Ryzen 7 1800X:
This update has been pushed to stable.
AMD info from older CPU (Athlon II X4 635):
@sezeroz modern CPUs all use variable speed stepping to save power; when they're idle they'll run much slower, basically. It's quite normal to see the speed of your CPU change often. Usually it'll have a 'floor' it never goes under, where it sits all the time when it's idle; looks like yours is probably 800MHz.
Just tested this on my Thinkpad X220; confirming bug #1532058 is fixed.
Seems to be also fixing "#1533654 - Two-finger scroll does not work after suspend-resume cycle." \o/
Installed on two different AMD systems. Didn't notice any differences from previous kernel. Output from the two AMD systems is below.
======================================================================= dmesg | grep Spectre [ 0.015059] Spectre V2 mitigation: Vulnerable: Minimal AMD ASM retpoline
grep spectre /proc/cpuinfo bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2
=========================================================================
dmesg | grep Spectre [ 0.017130] Spectre V2 mitigation: Vulnerable: Minimal AMD ASM retpoline
grep spectre /proc/cpuinfo bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 bugs : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2
Works for me and fixes bug #1514969 on one of my machines.
works