They have a flaw, but it's fixable with a microcode update. If the update will have any drawbacks is still unknown.
It would be fixed in a firmware update or else in the macOS kernel, from what I gather. So not a big deal.Has Apple ever rolled out a processor microcode patch that is user installed?
Or is this something that would be a recall ?
The bug affects all computers with Intel Skylake and Kaby Lake processors irrespective of OS. It is unlikely that Apple rather than Intel will develop the patch but Apple will nearly certainly offer it to their customers when Intel completes the patch.So if I understand correctly
Not really an OS X problem
Not likely to see the issue under normal circumstances
Apple will be able to patch around it.
In my opinion, the nature of this bug and what the CPU does going into and coming out of sleep doesn't make it likely that your problems are caused by this bug. You can try this out and disable hyper-threading and see if you have any more issues. If your problem is occasional, the fix may happen before a crash happens again. My guess would be that you will continue to have the same sleep issue after the fix.I have occasional CPU crash that happens in different apps during sleep sometimes which causes a Kernel panic and a reboot. I attribute this to this bug, so I hope Apple patches in the microcode in next Sierra patch or in High Sierra.
I listened to the podcast live and definitely recall Steve Gibson mentioning the bug as a security vulnerability but he only did so in passing. If the bug didn't pose a security concern Steve would not have covered the issue at all.So I looked at the transcript of the podcast of "Security Now!" which is referenced in post #9. Their podcast talked about multiple topics, the Skylake/Kaby Lake bug being one of them. They did not mention it as being a security concern. I read the part where they talked about the bug (skimmed the rest) so if I'm missing something, please let me know. The concern of this type of bug would be somebody launching a denial-of-service attack on a computer which has a web presence. I don't think many coders with evil intents dropped what they were doing to work on exploiting this bug. Maybe some coders with mischievous intents would find this interesting.
I have a Skylake computer and a website on AWS (who knows if it's running on Skylake or Kaby Lake). This is not something I losing sleep on.
You base your opinion on what? Ars said that the bug may cause cpu crashes which is always the reason for the restart of my Mac according to reports.In my opinion, the nature of this bug and what the CPU does going into and coming out of sleep doesn't make it likely that your problems are caused by this bug. You can try this out and disable hyper-threading and see if you have any more issues. If your problem is occasional, the fix may happen before a crash happens again. My guess would be that you will continue to have the same sleep issue after the fix.
I based what I said on what I read in the transcript, which may be edited from the podcast. I'm not the one concerned about this bug being a major security concern. If you disagree with my assessment of the risk, I wouldn't mind being corrected by Steve Gibson but you should be the one contacting him as you're the one who's using him as basis for saying this poses a notable security risk.I listened to the podcast live and definitely recall Steve Gibson mentioning the bug as a security vulnerability but he only did so in passing. If the bug didn't pose a security concern Steve would not have covered the issue at all.
Steve did not cover any specifics of how the bug might be exploitable or how easy or difficult it might be to do so and I would doubt that he would discuss this as long as the bug remains unexploited and unpatched. If you contact Steve and ask generally how bugs of this nature are typically exploited and what your level of concern should be he would probably answer that much.
I haven't programmed for sleep and wake in OSX, but I have in iOS and from the documentation, it's works in a similar fashion. You have to ask the OS for the sleep/wake notification and then code for these notifications. For sleep, you stop any active processes and save state. It's hard to see how the bug affects the preparation for sleep because if there was an issue, it should have happened BEFORE the sleep. The OS will wait until all applications have completed their sleep preparations before doing the work it needs to sleep. Waking is a more chaotic situation than preparing for sleep and on iOS at least, different events don't always occur in the same order and for my app at least, which had to deal with possibly restarting network connections, it was a trial-and-error process as to what worked and what didn't on a consistent basis when dealing with the network connections. What's happening in the waking process is having the CPU restore state for the OS in general and the applications that requested the wake notification. As is the case with my app, there may be the need to get the hardware back in order (so maybe re-opening a file, etc.). From the reading of how the bug works, it appears that it makes intensive use of the registers and requires prolonged use to make it appear. I don't think the type of work done on wake - restoring state and making sure hardware connections are restored, etc., is register intensive and it certainly isn't prolonged. Now, if one has a CPU-intensive process that starts up on wake, that may be a different story but if one can't get that CPU-intensive process to fail when not sleeping, the chances of it failing immediately upon waking seems small to me. Most sleep issues are due to the chaotic nature of wake that I described, especially if you have an app that doesn't ask for sleep/wake notifications or hasn't been tested extensively on the particular hardware/OS one is using.. Also, Apple doesn't have a lot of experience with either the Skylake or Kaby Lake processors used in the MBP, comparatively speaking so there may need to be some tweaking that they need to do as it relates to the sleep/wake process. There's just so many variables in the sleep-wake programming and processing and for me, it just seems that this particular bug should not be on the top of anybody's list as the culprit of sleep-wake issues.You base your opinion on what? Ars said that the bug may cause cpu crashes which is always the reason for the restart of my Mac according to reports.
It's hard to test as the issue happens rarely, I would have to run my Mac without hyperthreading for a week to see if it works.