Arthur T Knackerbracket has found the following story:
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 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.
Also at Tom's Hardware and Ars Technica.
(Score: 2) by shortscreen on Tuesday June 27 2017, @09:08AM (2 children)
I guess modern compilers don't use AH,BH,CH,DH much huh? When Intel was testing out their fresh chips they must have forgot to run some vintage hand coded assembly.
(Score: 1, Informative) by Anonymous Coward on Tuesday June 27 2017, @09:40AM (1 child)
From the description, emphasis by me:
I cannot imagine any 64 bit code that doesn't use RAX, RBX, RCX or RDX, nor any 32 bit code that doesn't use EAX, EBX, ECX or EDX.
(Score: 2) by Dr Spin on Tuesday June 27 2017, @02:24PM
The way I understood this, the bug is tripped when you use the 8 bit reg in one thread and the extended reg
in another thread.
Have I read it wrong?
(I read the OpenBSD description, but on a phone, without my glasses).
I suggest that this is more evidence that a monoculture is high risk. I can't wait to see Arm servers able
to compete on performance in the "8 to 64 thread" market. It would be nice to see greater diversity in
memory interfaces too.
Warning: Opening your mouth may invalidate your brain!