Monday, January 22nd 2018
Intel Announces Root Cause of Meltdown, Spectre Patch Reboot Issue Identified
Intel has finally come around towards reporting on the state of the reboot issues that have been plaguing Intel systems ever since the company started rolling out patches to customers. These patches, which aimed to mitigate security vulnerabilities present in Intel's chips, ended up causing a whole slew of other problems for Intel CPU deployment managers. As a result of Intel's investigation, the company has ascertained that there were, in fact, problems with the patch implementation, and is now changing its guidelines: where before users were encouraged to apply any issued updates as soon as possible, the company now states that "OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions, as they may introduce higher than expected reboots and other unpredictable system behavior." A full transcription of the Intel press release follows."As we start the week, I want to provide an update on the reboot issues we reported Jan. 11. We have now identified the root cause for Broadwell and Haswell platforms, and made good progress in developing a solution to address it. Over the weekend, we began rolling out an early version of the updated solution to industry partners for testing, and we will make a final release available once that testing has been completed.
Based on this, we are updating our guidance for customers and partners:
I will keep you updated as we learn more and thank you for your patience."
Sources:
Intel NewsRoom Reboot Issues, Intel newsRoom Udpated Guidance
Based on this, we are updating our guidance for customers and partners:
- We recommend that OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions, as they may introduce higher than expected reboots and other unpredictable system behavior. For the full list of platforms, see the Intel.com Security Center site.
- We ask that our industry partners focus efforts on testing early versions of the updated solution so we can accelerate its release. We expect to share more details on timing later this week.
- We continue to urge all customers to vigilantly maintain security best practice and for consumers to keep systems up-to-date.
I will keep you updated as we learn more and thank you for your patience."
41 Comments on Intel Announces Root Cause of Meltdown, Spectre Patch Reboot Issue Identified
crashes are binary, so bad implies there is some amount of bad that can be accepted, but this is 'some reports came in so ctrl+z', ubuntu recently had some laptop firmware losing issue that no other distro had, so sometimes it's not even the microcode's problem but what the distro was trying to do (edit: was update #1 this or was it still meltdown?) ubuntu dropped their unity work & switched to gnome made by red hat, already on systemd made by red hat, people dont 'follow' ubuntu, they follow upstream changes that may or may not match what ubuntu does (if it isnt obvious, i dont like ubuntu or the way some packages are handled) who cares what a few people said on some forum? at a subconscious level it's boasting about your setup so it adds too much filler text (yes, ironically i want an evolved reaction from you even though we have nothing to do with each other & nobody cares tomorrow... if anything, not feeling the need to be defensive will bring you peace while the others stay stressed, letting go of an argument is applicable to both sides not just the attacker (disclosure: i saw your old posts the first time though it's good that i had a few days to think about them more & reread them today))
your browser is losing performance because they loosened a certain timer latency, not that it will be noticable, neither is the touted 30% loss that people keep reposting... that loss is extremely specific & probably most obvious on an SSD where speeds are crazy high, 0.1s to 0.5sec is a multi hundred percent loss, but still less than a second, so i dont avoid updates without measuring or at least noticing losses for myself (even if they exist, in a game example, 90 to 85 fps is irrelevant, winxp might be faster sometimes, but not enough to matter, deferring updates could be in the same situation)
edit: by the way, work has been done since the summer, but i guess a lot of rushing was going on in january
Now please tell me which one of us was the one acting foolish. Me, using my judgement to determine that it would be wiser to wait until this is sorted out? Or you, downloading and deploying untested beta software designed to gimp CPU's, that now even the ones who made it say it would be better to uninstall? It's one thing to call someones actions foolish and then falsely pretend that the actions of someone doesn't say anything about his character and somehow his actions are separated from him and you can belittle them at your own leisure without insulting him by one bit. It's something else though when your own actions fall under the exact definition of the words you projected on someone else while his are the exact opposite. This says a lot about the character of a person who goes out and projects his own flaws unto others. Please, in the future, instead of worrying about what other people do and judging their actions, take some time out and think better about yours. Use the time you would waste trying to judge others to improve yourself, because it seems that you really need it. This advice goes out to kn00tcn too because he, as any good Canadian does, seems to be more interested in other's people's business than his own...
(of a person or action) lacking good sense or judgment; unwise.
Note the bold.
Look, if you want to take offense, I can't stop you. I can only state my intent and hope for the best.
The rest of your post is full of unnecesary implications that I feel would be counterproductive to reply to.
You seem a very angry person. For that reason, I'm out.
I'm sorry I made you mad. It wasn't my intention but it is what happened. Truth be told, I don't feel too guilty about it as it seems you are abusing definitions to make yourself angry and I never really intended insult, so what more can I do but say "sorry, didn't mean to make you mad bro?" I can't help but infer that that may mean you are an angry person, if you aren't and are thinking of rainbows right now, please be pleased to know I am happy for you.
Good day.
So I'm sorry. I did not mean to hurt your feelings by telling you a security patch may be important.
I'm glad you are happy. Enjoy your 5-10% performance edge and be careful with that security hole.
By the way, this microcode patch was not deployed to Ryzen CPUs, which I am using. So... yeah. I've really got no point except to offer my advice and feelings on best practices. Yes, I feel you are being foolish still. I am sorry that offends you but my thoughts are my own.
My tower (running Ubuntu "Desktop" 17.10):
...and the tower in the attic crunching with Ubuntu "Server" 17.10:
So, other than the fact that I haven't updated Smite in a while, they're using the same kernel and the same packages, yet one is "desktop" and the other is "server". The only difference is what packages are installed when the OS was installed for the first time but, I can install Ubuntu Server, run "sudo apt install ubuntu-desktop" and there is literally no difference from Ubuntu Desktop. In fact, every package is addative, it doesn't remove packages when going to desktop, so what gets installed on server is just a subset of what gets installed on desktop. Likewise, if I did a desktop installation and removed just about every package for anything GUI-related and that Ubuntu Desktop will be in [roughly] a state that is the same as a Ubuntu Server installation (uninstalling packages is never as clean as never installing them.)
Either way, Ubuntu Server is not distinct from Ubuntu Desktop, the only difference is what you start with. Even the one thing that used to be different, isn't anymore (the kernel.) Even the /etc/apt/sources.list are practically identical for all Ubuntu apt repos. So, I'm calling foul. There is a reason why the alternative installer doesn't exist anymore, because that's the GUI-less server installer. It's really not any different. In fact, if you want a minimal or mimimal VM installation, desktop or not, you use the server installer but, there is legit no difference between the end result other than what packages are there after installation but, I can assure you that every package in a base server installation is the same as desktop when you talk about Ubuntu's apt repos.
Also, I've read somewhere that the first microcode update caused some chips (specifically Haswell and Broadwell?) to report "internal errors" on HWInfo64, can anyone with an updated microcode confirm this, please?
I was simply wondering if there were different microcodes for different processors that perhaps had different effects?