Comment by ourcat

9 years ago

So will this be affecting most Macbook Pros of the past few years?

If so, there's a way to disable hyper-threading, but you need Xcode (Instruments).

Open Instruments. Go to Preferences. Choose 'CPU'. Uncheck "Hardware Multi-Threading". Rebooting will reset it.

15 comments

ourcat

Reply
yborg  9 years ago

This is kind of like cutting off your leg because of a hangnail. I've been running a Skylake MBP for more than 6 months for compilation workloads and haven't seen a single processor hang.

I'm much more annoyed by the completely unpredictable desktop assignment on monitors when hotplugging DisplayPort connections on multiple displays. This one bothers me every day.

  • codezero  9 years ago

    That's weird re monitor issues. I've been impressed with how consistent mine are.

    What I see:

    Same monitor/monitors plugged into same ports produce consistent configs.

    I get a unique config per monitor/port.

  • ourcat  9 years ago

    I agree. I've been fine myself. But if people feel the need to turn it off. ;)

rayiner  9 years ago

No. Even though Skylake came out in 2015, Apple used an older CPU (Haswell) until the October 2016 MacBook Pros.

  • reaperhulk  9 years ago

    They used Skylake in late 2016 MBPs and Kaby in the 2017 models.

    • isatty  9 years ago

      I'm on a Kaby

          Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz

      I haven't seen any erratic crashes yet on code compiled by LLVM 8.1.0 on multiple projects (ROS, Qt5). I hope a microcode fix is pushed by Apple on behalf of Intel soon.

      4 replies →

rsynnott  9 years ago

From one of the 2016 MacBook Pros:

> machdep.cpu.model: 78 > ... > machdep.cpu.stepping: 3 > ... > machdep.cpu.microcode_version: 174

Can't find if 174 is the fixed version or not.

So this is one of the models for which there exists a fix, as per the email.