Slashdot Mirror


Intel Urges OEMs and End Users To Stop Deploying Spectre Patch As It May 'Introduce Higher Than Expected Reboots' (intel.com)

Intel executive vice president Neil Shenoy said on Monday that the chip-maker has identified the source of some of the recent problems, so it is now recommended that users skip the available patches. From the blog post: 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.

88 of 155 comments (clear)

  1. Oh? by jawtheshark · · Score: 5, Insightful

    You mean like, more than zero? Apart from a planned a kernel upgrade I never reboot. My systems also don’t reboot spontaneously.

    --
    Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    1. Re:Oh? by Anonymous Coward · · Score: 1

      Apart from a planned a kernel upgrade I never reboot.

      I thought my daily reboots would go away when I upgraded to WinME. No such luck.

    2. Re:Oh? by OrangeTide · · Score: 1

      My systems also don’t reboot spontaneously.

      You're going to love these patches then. Life is full of new experiences. :(

      --
      “Common sense is not so common.” — Voltaire
    3. Re: Oh? by Anonymous Coward · · Score: 1

      You clearly only have a few hundred servers. If you had thousands you would start to notice several unexplained reboots year. Some you would blame on hardware, others on software, some would be unexplained. You might post your kernel dump expecting some sort of mass panic that you had found a crash but most likely it would just go with the thousands of other crash reports and you would realise that kernels are full of unfixed undiagnosed bugs.

    4. Re:Oh? by arth1 · · Score: 1

      I thought my daily reboots would go away when I upgraded to WinME. No such luck.

      The "reboot at least every 43 days" bug that plagued Windows 98 went away when upgrading to Windows Me, though.

    5. Re:Oh? by sconeu · · Score: 1

      Because it never stayed up 43 days in a row.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    6. Re:Oh? by nmb3000 · · Score: 2

      It is a pretty remarkable euphemism. Imagine prescription drugs had disclaimers written like this:

      "Notice: This product may introduce higher than expected deaths."

      Sign me up!

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
    7. Re: Oh? by Xenx · · Score: 1

      Exactly.It becomes a matter of whether the benefits of the medication outweigh the symptoms or risks they introduce.

    8. Re:Oh? by aliquis · · Score: 1

      My dad died in pneumonia after having being given Risperdal while he had Alzheimers, something the FDA recommends against doing considering exactly that. I don't know if the manufacturer say so themselves but supposedly it is the case.

    9. Re:Oh? by Erik+Hensema · · Score: 1

      When you're running thousands of systems, spontaneous reboots happen. Could be due to some power fluctuation caused by a flaky PSU for example. Intel's now saying that the expected number of spontaneous reboots has risen with the new microcode.

      When running a few systems you shouldn't notice spontaneous reboots.

      --

      This is your sig. There are thousands more, but this one is yours.

  2. good by Anonymous Coward · · Score: 1

    Iâ(TM)m glad they are telling us to leave our systems insecure, that is helpful advice

    1. Re:good by DCFusor · · Score: 1

      Maybe someone will make an app that makes iPhones actually work right on the internet....Nah.

      --
      Why guess when you can know? Measure!
    2. Re: good by Monster_user · · Score: 1

      It is a simple toggle switch in the settings. "Smart Quotes". Users just have to find it, and switch it to the off position.

      Be fancy, or be functional. The iPhone on iOS 11 can't do both.

    3. Re: good by DCFusor · · Score: 1

      Too bad I used up all my mod points and now can only comment. So, the iPhone users are just not capable of adapting to Slashdot?

      --
      Why guess when you can know? Measure!
    4. Re: good by Monster_user · · Score: 1

      I'd say so. Not like Slashdot is a multimillion dollar company with a massive labor force geared towards the user experience.

      As soon as I saw this iPhone 7 was affected following the upgrade to iOS 11, I searched for the option to turn that feature off. I can confirm it is present in 11.2.

  3. Good Timing by Templer421 · · Score: 1

    Couldn't be bothered to do it right the first time.

  4. Higher than... what? by dos1 · · Score: 4, Funny

    "Higher than expected reboots"? What kind of newspeak is it?

    1. Re:Higher than... what? by PingSpike · · Score: 5, Funny

      Its like how a car with a rusted out brake lines has a higher than expected number air bag deployments. You expected zero but Intel has exceeded all expectations once again.

    2. Re:Higher than... what? by Anonymous Coward · · Score: 1

      "Higher than expected reboots"? What kind of newspeak is it?

      Well, it sounds better than "random system crashes caused by a shitty, untested patch we rushed out the door".

      Intel has seriously shat the bed on this one.

    3. Re:Higher than... what? by gweihir · · Score: 3, Insightful

      It means "we will continue to fuck you with shoddy products". Linus is right on the mark for this one.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    4. Re:Higher than... what? by DontBeAMoran · · Score: 2

      Maurice Moss: [picking up the phone] Hello, IT... Have you tried forcing an unexpected reboot?

      --
      #DeleteFacebook
    5. Re:Higher than... what? by bettodavis · · Score: 2

      Slightly more than a working computer, slightly less than a doorstop brick.

    6. Re:Higher than... what? by ReneR · · Score: 1

      yeah, wanted to write exactly the same. I expect zero, yes 0, null, nil, absolute no unexploded reboots from my CPU, ..!

  5. How About New Silicon, Then? by Anonymous Coward · · Score: 1

    When can we deploy that, Intel?

    1. Re:How About New Silicon, Then? by Anonymous Coward · · Score: 1

      whenever NSA signs off on the new backdoor.

    2. Re:How About New Silicon, Then? by DontBeAMoran · · Score: 4, Funny

      Fuck Intel. Enough is enough. I'm ordering four billion transistors on digi-key right fucking now.

      --
      #DeleteFacebook
    3. Re:How About New Silicon, Then? by zwarte+piet · · Score: 1

      Wire wrapping this baby

  6. So um... How many reboots by rsilvergun · · Score: 1

    Was Intel expecting? Me, I was expecting one to install the patch. I guess anything more is, technically, higher than expected. Also, this kind of mealy mouthed garbage is why Linus is so made at you right now Intel...

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:So um... How many reboots by Anonymous Coward · · Score: 1

      I believe you answered your own question.

    2. Re:So um... How many reboots by arth1 · · Score: 1

      Was Intel expecting? Me, I was expecting one to install the patch.

      You don't need a reboot for the Intel patches. Those are microcode updates, which can be applied on a running system.

      (Reverting to an earlier version of microcode requires a reboot, though.)

  7. Intel has known about the vuln for almost 7 months by Hadlock · · Score: 5, Informative

    Did they just roll out a patch in the last 30 days, or what's going on over there? This is the kind of instability one would expect from a hastily produced patch developed over a month by a small team. According to reports, Intel has known about the vuln for 7+ months. Were they not working on a patch this whole time? I would assume they were on iteration 5 or 6 of the patch by the time they broke the embargo a week early.

    --
    moox. for a new generation.
  8. "Higher than usual" my ass by Anonymous Coward · · Score: 1, Informative

    Some famous person should finally bomb intel over their "higher than usual" BS. It's an insult to every single person who's reading this idiotic Slashdot news post. Non-broken "systems" don't have "unexpected reboots" ever. FFS.

  9. Re:Intel has known about the vuln for almost 7 mon by Narcocide · · Score: 4, Insightful

    They thought they spent enough money astro-turfing that they wouldn't need to spend any more developing a patch. When the astro-turfing campaign failed, they had to scramble to produce something that nobody would use but that everyone would believe was "best effort."

  10. Looking forward to Linus's response... by forkfail · · Score: 5, Interesting

    ... to Intel's announcement.

    Especially given what he had to say about the patches in the first place:

    http://lkml.iu.edu/hypermail/l...

    --
    Check your premises.
    1. Re:Looking forward to Linus's response... by HiThere · · Score: 1

      You may wait awhile. For Linus to comment on patches is reasonable. He rarely comments in an interesting way on things that he has criticized being withdrawn.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:Looking forward to Linus's response... by MikeBabcock · · Score: 1

      As with all things Unix, you're supposed to generate output on failures, not success.

      --
      - Michael T. Babcock (Yes, I blog)
    3. Re:Looking forward to Linus's response... by MikeBabcock · · Score: 1

      I missed that one somehow, that was fantastic. Almost to the level of his famous nvidia rant.

      --
      - Michael T. Babcock (Yes, I blog)
  11. The inevitable result of "ready, fire, aim" by SlaveToTheGrind · · Score: 1

    Maybe it's time for a slightly more measured approach?

    1. Re:The inevitable result of "ready, fire, aim" by RhettLivingston · · Score: 4, Insightful

      The fact that they took half a year to deliver this cluster**** could be an indicator that no true "fix" is possible or that the performance losses of a true fix would have a far worse overall impact than just accepting random reboots.

      I understand that they'd likely need a multi-government bailout and years of production time to replace all of the broken processors, but facing reality and moving forward with a real fix feels like the healthiest thing for the system as a whole. How much time and money is being wasted worldwide by IT folks and software engineers on this fiasco?

    2. Re:The inevitable result of "ready, fire, aim" by el+borak · · Score: 4, Insightful

      The fact that they took half a year to deliver this cluster**** could be an indicator that no true "fix" is possible or that the performance losses of a true fix would have a far worse overall impact than just accepting random reboots.

      You're assuming they spent half a year working on a fix. I think it's far more likely that:

      2 months were wasted by engineers trying to convince management that the problem really was potentially very serious

      2 months waiting for management to try to figure out who to blame and how to make sure it wouldn't reflect negatively on them or impact their departmental budget or personal performance bonuses

      1.5 months for PR to come up with the best possible language to make sure they could paint the entire industry as being equally affected, while simultaneously the lawyers tried to find the largest possible scraps of TP to cover their corporate *sses

      .5 months working on a fix

      --
      An imperfect plan executed violently is far superior to a perfect plan. -- George Patton
    3. Re:The inevitable result of "ready, fire, aim" by SlaveToTheGrind · · Score: 1

      Do we really know they were actively working on a fix for half a year? I hadn't seen anything but speculation to that effect, but may have missed it.

    4. Re:The inevitable result of "ready, fire, aim" by Brett+Buck · · Score: 1

      This - it's not truly fixable.

    5. Re:The inevitable result of "ready, fire, aim" by Anonymous Coward · · Score: 1

      You skipped 2 months having a few engineers trying to convince their peers that this is real. Don't discount the effects of self-indoctrination when you've been telling yourself and your peers that this clever, patented hack that beats the competitors is perfectly safe and any imaginable attack is "purely academic."

    6. Re:The inevitable result of "ready, fire, aim" by Rockoon · · Score: 1

      Do we really know they were actively working on a fix for half a year?

      We know that they should have been.actively working on a fix for half a year.

      --
      "His name was James Damore."
  12. He should have just said... by Andrew+Lindh · · Score: 5, Insightful

    "We recommend everyone stop deployment of Intel CPUs". Higher than expected reboots? More than 1 to install the update? The root cause is design flaws and inadequate testing of major low level patches. Google new about these issues months ago and Intel did (or should have) too. They rushed the release so the stock price does not tank not because it was ready. They normally take many months or years to test these design changes or updates and now it will be a long time before they have new CPUs that don't need fixes (or at least these fixes). May be they should have worked around the clock months ago when they did not need to be rushed.

    1. Re:He should have just said... by Andrew+Lindh · · Score: 1

      I had better issue a patch for that.

    2. Re:He should have just said... by HiThere · · Score: 3, Informative

      Spectre is nearly everyone but the Raspberry Pi. Meltdown is just Intel. And Meltdown is the one that's (currently) really serious.

      I'm rather sure that Spectre will eventually be serious, so people need to be working HARD to solve it, but Meltdown is the currently critical one, and that's just Intel.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    3. Re:He should have just said... by thegarbz · · Score: 1

      Meltdown is just Intel.

      Well technically Meltdown is also IBM. The Power7 through 9 are affected.

  13. Their Problem could be by oldgraybeard · · Score: 4, Insightful

    The only way to truly fix things is to replace the CPU. And that would really hurt/destroy Intel's bottom line.

    Which leaves them flailing about wildly for some other appearance of a solution/solution to, at the very least cover their butts, mean while costing them a little as possible.

    Just my 2 cents ;)

    1. Re:Their Problem could be by nwf · · Score: 3, Insightful

      Replacing the CPUs is likely something they can't do anytime soon, since I'd guess none of the next 2 years worth of CPUs will have a fix for this. Spectre can't be fixed in the general case, I believe.

      Replacing is really the only viable option for performance-critical applications (which most users don't have), but Intel is never going to give them out. I can see after some massive lawsuits that they offer a 10% discount on a new CPU (for which you need a new motherboard). It's likely going to help their bottom line.

      --
      I don't know, but it works for me.
    2. Re:Their Problem could be by HiThere · · Score: 1

      I'm sure that Spectre *can* be fixed, though we may not currently know the best way. But Meltdown is the current real problem (as opposed to the problem a few months from now, when a new exploit is revealed).

      And it's my guess that Intel can't fix Meltdown in any of it's current chips without disabling speculative execution entirely. Which, of course, would solve Spectre, but would also make them a LOT slower than AMD.

      And by "Intel's current chips" I'm including all those whose masks have already been designed, not just the ones currently shipping.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  14. "Unexpected reboot" by hey! · · Score: 3, Insightful

    In other words their patch crashes your machine.

    This reminds me of the various colorful circumlocutions people around the world use for death. In France someone who dies "eats daisies by the roots". In Germany he "gives up his spoon". In China he "goes to sell salted duck eggs."

    I suppose in Intel-speak death would be "non-transitory pulmonary quiescence."

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:"Unexpected reboot" by sexconker · · Score: 1

      Bought the farm.
      Bit the dust.
      Kicked the bucket.
      Pushing up daisies.
      Taking a dirt nap.
      Sleeping with the fishes.

    2. Re:"Unexpected reboot" by sconeu · · Score: 1

      Ceased to be.
      An EX-PARROT!!!

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    3. Re:"Unexpected reboot" by Khyber · · Score: 1

      Sailors used that term LONG before any Italian Mafia existed.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    4. Re:"Unexpected reboot" by sexconker · · Score: 1

      Late.
      Stiff.

    5. Re:"Unexpected reboot" by Anonymous Coward · · Score: 1

      Shuffled off this mortal coil.
      Paid the debt that cancels all others.
      Turned toes up to the daisies.
      Became food for worms.
      Became a permanent man of leisure.

    6. Re:"Unexpected reboot" by Jayfar · · Score: 1

      Nah, it's just pining for the fjords.

  15. Bravo Intel by bigdady92 · · Score: 1

    Golfclap?
    Golfclap

    *GOLFCLAP*

    --
    Wheel of Time: Book by Book and Sumview (summary review) Bigdady92 style: http://bigdady92.blogspot.com/
  16. That's how its supposed to work? by Arzaboa · · Score: 4, Funny

    Can't steal data from a CPU while its power cycling!

    --
    Round and a round and a round we go

    1. Re:That's how its supposed to work? by mxh · · Score: 1

      Exactly!
      Can't steal anything when my Xeon running win7 is "patched" like this:
      Xeon X5680 after KB4056894

  17. Intel has known about the vuln for almost 7 months by Futurepower(R) · · Score: 1

    "According to reports, Intel has known about the vuln for 7+ months."

    Re-post: Intel: Years of insufficient management.

  18. Pooched patches by gettin2old · · Score: 1

    So after having months and months to create a patch to their borked design, they fail.
    Now in a few measly weeks (days) they have a real patch that's going to do the job.
    For everyone (including me) that started performance testing patches before you deploy them.... back to Step 1.

  19. Smoking causes higher than expected deaths by JoeyRox · · Score: 1

    Whereas eating a healthy diet and exercising regularly causes fewer than expected deaths.

    1. Re:Smoking causes higher than expected deaths by DCFusor · · Score: 1

      100% die, it's only a matter of when. What planet are you from?

      --
      Why guess when you can know? Measure!
    2. Re:Smoking causes higher than expected deaths by JoeyRox · · Score: 1

      Planet Immortal Senk i 5 - it's right next to Uranus.

    3. Re:Smoking causes higher than expected deaths by DCFusor · · Score: 1

      +1 Funny!

      --
      Why guess when you can know? Measure!
  20. Re: Intel has known about the vuln for almost 7 mo by Anonymous Coward · · Score: 1

    "In any case, [Intel] failed us"

    Dude: Intel is a corporation. It's certainly seems to have done very well for those that matter... it's shareholders. Are you a shareholder?

    If otoh, you want to buy chips from somewhere beholden and accountable to the public, help figure out the Open Hardware movement.

  21. Re:Fuck Intel... by mark-t · · Score: 3, Interesting

    Expect to be waiting quite a while then.... I have a strong feeling that Intel simply doesn't know how to do a proper fix for this that isn't just another kludge on any processor they will be making for the forseeable future that has already passed through its design phase.

    That's not to say that I think they won't figure one out, eventually... but I'd honestly be surprised if we see a proper fix (one that isn't just a hack-on patch that works at a cost) before 2020.

  22. so... the patches are as bad as the processors? by swschrad · · Score: 1

    Intel Doeshide.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
  23. It's gets worse! by Gravis+Zero · · Score: 4, Funny

    Not only has the microcode patch caused unexpected reboots from Intel's CPUs but it's also causing spontaneous AMD purchases! ;)

    --
    Anons need not reply. Questions end with a question mark.
  24. So that's the meaning of "Intel Inside" by Mister+Liberty · · Score: 1

    "Unpredictable system behavior".

  25. I bought two CPUs last year by rsilvergun · · Score: 3, Interesting

    and plan to look into the class action suits. Had I known I would have held off or bought a Ryzen. I'm not expecting Intel to buy me new CPUs but as a gamer the 5-10% hit I'm seeing will eventually caught up to me and force an upgrade sooner than intended.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:I bought two CPUs last year by thegarbz · · Score: 1

      but as a gamer the 5-10% hit I'm seeing

      That's quite interesting given that this isn't born out in any of the very many benchmarks that have been done on this. There were plenty to show that gamers experience precisely zero difference. There were more that show in most cases if your CPU is only a year old and has PCID you won't see anything near a 10% hit.

      Now if you said you were a server administrator and your corporate webserver or backend database started chugging, that would be quite believable.

      But by all means class action away. I'm sure the $10 discount you get for your new Intel CPU will be worth it when the new CPU is $20 more to recover the cost of the lawsuit.

      Ok that last sentence was a low blow, but the first was quite real, do you have a link to some real world figures on the effects of the patches, because looking into it extensively last week I concluded it was a non-issue for a gamer and the only thing likely to notice on my system is slightly lower throughput on my SSD.

  26. Re:Why does anyone even bother patching Spectre? by jbmartin6 · · Score: 4, Informative

    Multiple exploits are available, aren't they?

    --
    This posting is provided 'AS IS' without warranty of any kind, implied or otherwise.
  27. Goodbye Intel, Hello AMD by Anonymous Coward · · Score: 1

    My next system will be AMD.

    Lack of ECC support in desktop SKUs, cheeping out on PCIe lanes and a string of zero integrity marketing doublespeak including campaign to conflate meltdown /w spectre and now "higher than expected reboot" being the main reasons.

    General existence of timing side channels against branch predictors has been public knowledge for at least 15 years. Now when a ridiculous UNRELATED problem is discovered in Intel silicon red alert spectre spectre spectre... they are breaking shit and causing real damage in the process just to cover their asses. Fuck 'em.

  28. Their new slogan by gettin2old · · Score: 2

    Intel Inside!
    (Sorry about your luck dude)

  29. SHIT! Better Dump my INTEL stock! by Anonymous Coward · · Score: 1

    Oh rite. Already did. http://www.businessinsider.com/intel-ceo-krzanich-sold-shares-after-company-was-informed-of-chip-flaw-2018-1

    When is that fucker going to be charged?

    1. Re:SHIT! Better Dump my INTEL stock! by frankenheinz · · Score: 1

      *That's* what they mean by Intel Inside (R) !

      --
      The law is not an ass. No really.
  30. Re:Why does anyone even bother patching Spectre? by sjames · · Score: 2

    The first link is a POC that a process can read it's own memory space and privilege level without explicitly accessing it. I wouldn't call it nothing since it could allow javascript to access scripts running in other tabs, but the utility is very limited compared to meltdown and browsers are already in the works that prevent it.

    Meltdown really is orders of magnitude worse.

  31. Well WTF Intel?!? by sabbede · · Score: 1
    So after all the trouble we went through (mostly me) at my company to push the patches and the constant demand from our parent company to provide progress updates amidst a global panic, now I'm what, supposed to undo it all and stay vulnerable?

    Go to hell Intel.

  32. Drug Warnings by StatFiend · · Score: 1

    Haven't you listened to the lawyer-speak at the end of pretty much every drug commercial? For instance, Breo Ellipta, an inhaler used to treat asthma has this warning "People with asthma who take long-acting beta2-adrenergic agonist (LABA) medicines, such as vilanterol (one of the medicines in BREO), have an increased risk of death from asthma problems." (Emphasis added)

  33. Re:Why does anyone even bother patching Spectre? by sjames · · Score: 1

    According to Google, you should enable full site isolation in the latest version of chrome and they have further mitigation in the works.

  34. Go look up Witcher 3 benches by rsilvergun · · Score: 1

    There's a hit there on the top end. Also in synthetics. I'm not currently seeing the frame rate dips because my GTX 760 bottlenecks that. In 5 years that won't be true (just like it wasn't true when I put that 760 on my old A10-5800). I don't upgrade my CPU & GPU in tandem. I tend to buy more CPU than I need and wait for the price of graphics to come down.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Go look up Witcher 3 benches by thegarbz · · Score: 1

      Interesting, thanks for pointing that out. The very first review I found showed a 9.8% penalty on Witcher 3 while zero penalty on most of the other games under test. Interestingly Witcher 3 also gave the highest frame rate, does that mean the rest of the games are GPU bound and Witcher 3 presents an unnaturally high CPU load?

      If so what is it about Witcher 3 that taxes the CPU more than other games? Isn't it just an 3rd person RPG?

  35. To be fair you need a 1080 to see the dips by rsilvergun · · Score: 1

    maybe a 1070. Both of those are way outside my price range. But so was the equivalent to the 760 I'm rocking now. Heck, the i5 I just bought only just now came down to what I was willing to pay (got it for $150 on sale at Fry's Electronics). But it's still overkill for all the games I play and will be for the next 5 years... if the performance doesn't tank due to patches. I mostly play console ports that are GPU bound.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  36. Re:Why does anyone even bother patching Spectre? by blind+biker · · Score: 1

    Did you even read that? First of all, the scenario in that example stores sensitive data in userspace - nobody does that. Second of all, and more critically, the code knew where to look for the data, which extremely unrealistic.

    --
    "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.