|FROM ||Ruben Safir
|SUBJECT ||Subject: [Hangout - NYLXS] Major intel bug with Generation 7 and Xeon chips
|From hangout-bounces-at-nylxs.com Sun Jul 2 12:40:13 2017
Received: from www.mrbrklyn.com (www.mrbrklyn.com [18.104.22.168])
by mrbrklyn.com (Postfix) with ESMTP id 824B5160876;
Sun, 2 Jul 2017 12:39:54 -0400 (EDT)
Received: from [10.0.0.62] (flatbush.mrbrklyn.com [10.0.0.62])
by mrbrklyn.com (Postfix) with ESMTP id C2656160876;
Sun, 2 Jul 2017 12:39:41 -0400 (EDT)
From: Ruben Safir
Date: Sun, 2 Jul 2017 12:39:41 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Subject: [Hangout - NYLXS] Major intel bug with Generation 7 and Xeon chips
List-Id: NYLXS Tech Talk and Politics
Content-Type: text/plain; charset="utf-8"
Disabling hyperthreading may be the best way to avoid newly discovered
By Jon Martindale =E2=80=94 Updated June 27, 2017 2:35 am
intel hyperthreading bug kaby skylake core i7 6700k =
Greg Mombert/Digital Trends
low maintenance cabin at case inlet puget sound retreat =
The best part of this minimalist Pacific Northwest cabin is outside the
best transforming homes apartments trans home 3 =
Why have 1 room when you can have 2? Our favorite transforming homes
Why it matters to you
Unexplained crashes while using Intel's sixth or seventh generation CPUs
could well be due to a bug with hyperthreading.
Update: Added Intel comment on the news.
A new bug discovered in the sixth and seventh generations of Intel=E2=80=99s
central processors can affect any chip with hyperthreading enabled.
Although a fix exists for some CPUs, it may be worth disabling
hyperthreading just in case you run afoul of its potentially quite
The microcode bug discovered in the Intel chips could, under certain
conditions, cause processors to behave erratically, leading to possible
application and system stability issues and even data corruption and
data loss, according to Debian.org. The problem can exist on any
operating system and will require a microcode update from Intel to fix
Since originally posting this article, Intel sent us a comment on the
news, suggesting that it began rolling out a fix for his bug several
=E2=80=9CWe have already identified this issue and addressed it with a fix =
started rolling out in April 2017. As always, we recommend checking to
make sure your BIOS is up to date, but the chance of encountering this
issue is low, as it requires a complex number of concurrent
micro-architectural conditions to reproduce.=E2=80=9D
The microcode fix for seventh-generation Kaby Lake processors is said to
be with motherboard manufacturers right now. It will be distributed as a
BIOS/UEFI update, so make sure to check your motherboard maker=E2=80=99s we=
to see if there=E2=80=99s a recent release. If not, you may want to contact=
directly, but disabling hyperthreading in the meantime may be worthwhile.
For sixth-generation Skylake processors, there is an additional option,
though updating your BIOS would be the best first step. The Debian wiki
has further instructions on updating the microcode yourself, though it
won=E2=80=99t be possible for all processors of that generation, and you wi=
need to jump through a few hoops first.
If it seems overly technical, we=E2=80=99d again recommend disabling
hyperthreading for now instead.
If you=E2=80=99re unsure whether your CPU is one of the potentially affected
generations, there are a few things you can do. Intel has lists of
processors from each generation alongside a notification of whether they
support hyperthreading, but you=E2=80=99ll need to make sure you know your =
model number. Fortunately finding that out is easy on Windows 10 PCs.
Simply right-click on =E2=80=9CMy PC=E2=80=9D select properties and you=E2=
=80=99ll be taken to
the system panel where your processor=E2=80=99s name and number will be lis=
in an easy to read manner.
Check your CPU against the lists, and if you find it could be affected,
take appropriate action.
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
Being so tracked is for FARM ANIMALS and and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013
Hangout mailing list