Found this on Guru3D this morning. http://www.guru3d.com/news-story/debian-project-warns-turn-off-hyperthreading-with-skylake-and-kaby-lake.html. I haven't noticed any adverse effect as far as SETI is involved, but I have noticed that others like Corel DVD Pro 11 and Outer Tech Cacheman was acting strangely. I uninstalled Cacheman because it was using way to much CPU and the DVD Pro was pausing and skipping as if the DVD was damaged. I'll have to turn off H/T until I get an update from Intel. So I may time out on some tasks.,

---

I don't buy computers, I build them!!

Thank u for the heads up!!! +1

---

_________________________________________________________________________
Addicted to SETI crunching!
Founder of GPU Users Group

Thanks for the post. I have 8 of them. All got patched this morning.

Debian have a package called Intel-microcode available in both Stretch and jessie-backports. From what I understand the microcode is a partial fix and you also need a BIOS update.

---

BOINC blog

Intel's response to a Tom's Hardware Guide request for information.

“We have already identified this issue and addressed it with a fix that 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.”

So if you're running Linux, disable Hyperthreading until your distro or motherboard provider supplies an update if you've been getting data corruption or random system weirdness, or if it makes you feel better. If you're running a currently supported version of Windows, and have updates enabled and they are up to date, then it's been taken care of. You could always check for a BIOS update if you want to make the fix non dependent on the OS you are running.

---

Grant
Darwin NT

For those running Arch or Arch-based distros it's pretty painless to enable the microcode updates. Did it to my main desktop (only one affected by this) yesterday and it's all working fine (obviously backup your bootloader config before doing).

https://wiki.archlinux.org/index.php/Microcode#Enabling_Intel_microcode_updates

---