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.
No. Even though Skylake came out in 2015, Apple used an older CPU (Haswell) until the October 2016 MacBook Pros.
Intel Skylake/Kaby Lake processors: broken hyper-threading
81–90 of 278 posts
Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#82Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#83Earlier quoted context omitted.
Go back to rust-land now :D
It was meant as a response to OP basically saying that hardware vendors make way fewer bugs that the software ones, which is true, but many bugs of software can arguably be attributed to hardware design, so it's not like they're without fault. Rust has nothing to do with it, not sure why even bring it up.
Ever since I moved from C to Java (I like low level stuff but the company I joined is such) I have been having one of three major problems - logic bugs, too many frameworks, causing bugs due to lack of in depth understanding of each one of them, and GC bottlenecks. Of all of them, I hate the GC ones the most.
Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#84So 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.
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.
Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#85Earlier quoted context omitted.
This is not a fair comment: Ryzen had a crash that can be triggered by compiling with GCC and a memory compatibility issue where it cannot run them at their nominal speed. Ryzen is a really young architecture, it already had like 6 stable patches of microcode and you can expect way more.
Still seems to be doing better than "turn off half of your processor, sorry no fix just buy a new one".
Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#86Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#87The problem description is short and scary: Problem: Under complex micro-architectural conditions, short loops of less than 64 instructions that use AH, BH, CH or DH registers as well as their corresponding wider register (e.g. RAX, EAX or AX for AH) may cause unpredictable system behavior. This can only happen when both logical processors on the same physical processor are active. I wonder how many users have experi…
CPU manufacturers do do huge amounts of testing, and Intel does formal verification of some functional units. The reliability is far better than most software, in part because making a new release costs billions.
Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#88Oh well... so far the machine (running Windows 10) has been stable minus one or two random lockups in 2 months of heavy usage which could be attributed to this. Guess I wait...
Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#89Earlier quoted context omitted.
No. Even though Skylake came out in 2015, Apple used an older CPU (Haswell) until the October 2016 MacBook Pros.
They used Skylake in late 2016 MBPs and Kaby in the 2017 models.
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.Re: Intel Skylake/Kaby Lake processors: broken hyper-threading
#90Earlier quoted context omitted.
i am more willing to accept software having bugs / failing. i have 0 tolerance for hardware to have bugs
I wonder if there's a CPU out there that doesn't have bugs.
yes it happens, but software bugs happen every day where as if your system blue screened every day you know dang well you'd be on the phone with the hardware vendor for a refund / new system.