In accordance with Intel's microcode revision guidance from March 6 MCU
rev 0xc2 is cleared on both Skylake H/S and Skylake Xeon E3 processors
that share CPUID 506E3.
Signed-off-by: Alexander Sergeyev
---
arch/x86/kernel/cpu/intel.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Hi,
the microcode revision guidance from Intel is revised once again [1] (1 Mar).
It looks like the following:
Intel document only clears the 0xc2 microcode on *some* parts with CPUID 506E3
(INTEL_FAM6_SKYLAKE_DESKTOP stepping 3). For the Skylake H/S platform it's OK
but for Skylake E3 which
Hello,
Intel released an updated microcode revision guidance [1] (8 Feb). The link is
available in press-release [2], but it's quite easy to miss.
Some microcode revisions that were blacklisted before are now tested and
pronounced production-ready:
Lines with “***” were previously recommend
I didn't fully match the updated revision guidance and spectre_bad_microcodes
I compared these lists and it seems that the only difference is about skylakes.
Everything else is covered by less-or-equal criteria on revision version.
Both desktop and mobile skylakes are stated to be unaffected
On Sat, Feb 03, 2018 at 07:20:21PM +0300, Alexander Sergeyev wrote:
# first bad commit: [549b4930f057658dc50d8010e66219233119a4d8] platform/x86:
dell-smbios: Introduce dispatcher for SMM calls
From source code (at 549b4930f057) it looks like dell_set_arguments() which
writes to `buffer` is
Mario,
Would you please try https://patchwork.kernel.org/patch/10194287/
And see if it cleans up this null pointer dereference?
Yes, it does.
Is there any estimates on when the patch will be merged into mainline? I want
to put something into my distribution bug tracker, but it's unlikely the
To make dell_micmute_led_set() work properly we need to ensure that either WMI
or SMM driver is already loaded and initialized.
From the looks of the call trace dell_micmute_led_set() is called from device
phase of initialization. Which means that there is a use of dell-laptop
interface while
+{ INTEL_FAM6_BROADWELL_X,0x01, 0x0b23 },
That's redundant since blacklisting 0x0b25 will also stop us from
using 0x0b23 anyway.
and 23 is the pre security version so known good.
But 0x0b23 is listed under "stop deploying these MCU revs" (page 4, row 4).
Has something
Commit-ID: e3b3121fa8da94cb20f9e0c64ab7981ae47fd085
Gitweb: https://git.kernel.org/tip/e3b3121fa8da94cb20f9e0c64ab7981ae47fd085
Author: Alexander Sergeyev
AuthorDate: Tue, 13 Mar 2018 22:38:56 +0300
Committer: Thomas Gleixner
CommitDate: Fri, 16 Mar 2018 12:33:11 +0100
x86/speculation
9 matches
Mail list logo