Slashdot Mirror


Intel Replaces its Buggy Fix for Skylake PCs (zdnet.com)

Intel has released new microcode to address the stability and reboot issues on systems after installing its initial mitigations for Variant 2 of the Meltdown and Spectre attacks. From a report: The stability issues caused by Intel's microcode updates resulted in Lenovo, HP, and Dell halting their deployment of BIOS updates last month as Intel worked to resolve the problems. Intel initially said unexpected reboots were only seen on Broadwell and Haswell chips, but later admitted newer Skylake architecture chips were also affected. Microsoft also said it had also seen Intel's updates cause data loss or corruption in some cases.

2 of 57 comments (clear)

  1. Cure is worse than the disease by JoeyRox · · Score: 5, Interesting

    It seems to me the best way for Intel to pevent Meltdown exploits is by disabling Intel's TSX functionality (which I believe microcode can do), along with OS logic to terminate processes which generate an excessive number of protection exceptions for the same portion of code. The TSX change will force an exploit to throw exceptions for the indirect-memory access loop that probes for data values, and the OS change will then identify processes incurring these repeated exceptions inside a single block of code and then terminating it.

    1. Re:Cure is worse than the disease by cfalcon · · Score: 3, Interesting

      > is by disabling Intel's TSX functionality

      fucking AGAIN? Really????

      > (which I believe microcode can do)

      Yes, it can definitely disable TSX functionality. Like when TSX launched with Haswell, but it was fucked up, so they disabled it with microcode.
      Or when they fixed the Haswell problem and launched it with Broadwell, but it was fucked up, so they disabled with microcode.
      Skylake, of course, fixed the Broadewell problem...

      But now you're saying that TSX is the issue again? And that it needs to be disabled AGAIN? How many fucking chip generations do we have to go through before transactional fucking memory doesn't get patched out because OOPS it crashes the box or OOPS it gives double-super-ultra-root to enemy spies?

      Are you SURE that TSX is the issue? I didn't see anything in the article about TSX being the problem, but I'm not really read up on this.