SoylentNews

"exec" writes:

Story automatically generated by StoryBot Version 0.2.2 rel Testing.
Storybot ('Arthur T Knackerbracket') has been converted to Python3

Note: This is the complete story and will need further editing. It may also be covered
by Copyright and thus should be acknowledged and quoted rather than printed in its entirety.

FeedSource: [TheRegister]

Time: 2017-06-25 23:29:12 UTC

Original URL: https://www.theregister.co.uk/2017/06/25/intel_skylake_kaby_lake_microcode_bug/ [theregister.co.uk] using UTF-8 encoding.

Title: Intel's Skylake and Kaby Lake CPUs have nasty microcode bug

--- --- --- --- --- --- --- Entire Story Below --- --- --- --- --- --- ---

Intel's Skylake and Kaby Lake CPUs have nasty microcode bug

Arthur T Knackerbracket has found the following story [theregister.co.uk]:

During April and May, Intel started updating processor documentation with a new errata note, and over the weekend we learned why: Skylake and Kaby Lake silicon has a microcode bug.

The errata is described in detail [debian.org] on the Debian mailing list, and affects Skylake and Kaby Lake Intel Core processors (in desktop, high-end desktop, embedded and mobile platforms), Xeon v5 and v6 server processors, and some Pentium models.

The Debian advisory says affected users need to disable hyper-threading “immediately” in their BIOS or UEFI settings, because the processors can “dangerously misbehave when hyper-threading is enabled.”

Symptoms can include “application and system misbehaviour, data corruption, and data loss”.

Henrique de Moraes Holschuh, who authored the Debian post, notes that all operating systems, not only Linux, are subject to the bug.

Intel's errata note (for example in this document [intel.com]), describes the issue like this:

Under complex micro-architectural conditions, short loops of less than 64 instructions that use AH, BH, CH or DH registers as well as their corresponding wider register (eg RAX, EAX or AX for AH) may cause unpredictable system behaviour. This can only happen when both logical processors on the same physical processor are active.

The issue went rose above obscurity when Mark Shinwell, a developer working on the OCamlL [ocaml.org] toolchain, contacted the Debian team to explain that the OCaml compiler triggered an Intel microcode issue.

Debian's post notes that Intel has documented the bug and its microcode fixes for Core 6th [intel.com] generation, Core 7th [intel.com] generation, Xeon v5 [intel.com] and v6 [intel.com], and Core 6th generation X series [intel.com].

For Debian users:

Other users will need platform-specific fixes, or for BIOS/UEFI upgrades to land from their system vendors. ®

-- submitted from IRC

Original Submission