Forum Moderators: open

Message Too Old, No Replies

Broken hyperthreading in Intel Skylake/Kaby Lake processors

Can cause application and system misbehavior, data corruption and los

         

iamlost

3:57 pm on Jun 25, 2017 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



From Debian lists (25-June-2017):
[WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading [lists.debian.org],

Note: my bold emphasis.

This warning advisory is relevant for users of systems with the Intel processors code-named "Skylake" and "Kaby Lake". These are: the 6th and 7th generation Intel Core processors (desktop, embedded, mobile and HEDT), their related server processors (such as Xeon v5 and Xeon v6), as well as select Intel Pentium processor models.

TL;DR: unfixed Skylake and Kaby Lake processors could, in some situations, dangerously misbehave when hyper-threading is enabled. Disable hyper-threading immediately in BIOS/UEFI to work around the problem. Read this advisory for instructions about an Intel-provided fix.

...

...it could cause spurious errors, such as application and system misbehavior, data corruption, and data loss.

...

Please note that the defect can potentially affect any operating system (it is not restricted to Debian, and it is not restricted to Linux-based systems).

keyplyr

9:23 pm on Jun 25, 2017 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Thanks for the heads-up iamlost.
Please note that the defect can potentially affect any operating system (it is not restricted to Debian, and it is not restricted to Linux-based systems)
But this *is* restricted to systems using Intel processors code-named "Skylake" and "Kaby Lake."

keyplyr

8:07 am on Jun 26, 2017 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Just bought a friend an i7 500GB SSD, 12GB, 14" 4k anti-glare matte screen, DVD, Windows 10 Pro notebook.

This is a great piece of hardware, and yes the i7 is a Kaby Lake. I see nothing critical as it is not in use yet. I'll get the microcode updated before then.