Well fairplay to MS, their update came W7 way for me this morning. I think it was waiting until the antivirus got updated to have to correct registry entry. No BSOD so i'll take that as a win on the gf's laptop. No noticeable lag for what she uses it for so that's another win. Another plus side, going through the ARM list it looks like my phone and the tablet aren't affected.
There's now a little am-I-at-risk-from-Meltdown-or-Spectre script for Linux users. Sample output on my AMD box: Code: blacklaw@trioptimum:~/git/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh Spectre and Meltdown mitigation detection tool v0.13 Checking vulnerabilities against Linux 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1' * Kernel compiled with LFENCE opcode inserted at the proper places: NO (only 37 opcodes found, should be >= 70) > STATUS: VULNERABLE CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2' * Mitigation 1 * Hardware (CPU microcode) support for mitigation: NO * Kernel support for IBRS: NO * IBRS enabled for Kernel space: NO * IBRS enabled for User space: NO * Mitigation 2 * Kernel compiled with retpolines: NO > STATUS: NOT VULNERABLE (your CPU is not vulnerable as per the vendor) CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3' * Kernel supports Page Table Isolation (PTI): NO * PTI enabled and active: NO > STATUS: NOT VULNERABLE (your CPU is not vulnerable as per the vendor) ...and my shiny new Intel-powered Dell: Code: blacklaw@xerxes:~/git/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh Spectre and Meltdown mitigation detection tool v0.13 Checking vulnerabilities against Linux 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1' * Kernel compiled with LFENCE opcode inserted at the proper places: NO (only 37 opcodes found, should be >= 70) > STATUS: VULNERABLE CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2' * Mitigation 1 * Hardware (CPU microcode) support for mitigation: NO * Kernel support for IBRS: NO * IBRS enabled for Kernel space: NO * IBRS enabled for User space: NO * Mitigation 2 * Kernel compiled with retpolines: NO > STATUS: VULNERABLE (IBRS hardware + kernel support OR kernel with retpolines are needed to mitigate the vulnerability) CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3' * Kernel supports Page Table Isolation (PTI): NO * PTI enabled and active: NO > STATUS: VULNERABLE (PTI is needed to mitigate the vulnerability)
So has your Intel not had an update Gareth? Looks like the AMD is set, vulnerable to just one Spectre variant (just one oh yay...).
Yeah, Canonical hasn't released the PTI patch or the recompiled kernels yet - aside from limited testing versions via PPA. Both machines are on exactly the same kernel version.
Understanding the performance impact of Spectre and Meltdown mitigations on Windows [Intel] Systems --Microsoft It's mainly aimed at those on Intel but...
Well then. Looks like I'll be going to ryzen as soon as the new chips are out then as when added to my PC already not working with more than 4gb or RAM these added performance losses make it even bigger of a deal.
I'm on a haswell-era pentium and i've not noticed any slowdown... though given it had bugger all in the way of grunt to begin with it's kinda hard to tell...
Ivy bridge here, not noticed any subjective slowdown with W7 but then it's only had Witcher 3 run on it. Then again not had the BIOS update yet, whether Asus will do one for a board as old as mine I have no idea - it definitely won't be in their first batch.
Oh dear Intel https://www.google.co.uk/amp/s/www....f-chip-flaws-before-u-s-government-1517157430 US government not sounding too happy that Intel knew of the problems and decided to tell Chinese firms, and hence the Chinese government, before telling anyone else.
Ironic that the supposedly capitalist government is complaining rather than the supposedly communist one when Intel told their biggest customers first, which is an action only compatible with capitalism.
I think they're thinking more along the lines that Chinese companies knew so the Chinese government knew. This at a time when the NSA and US government didn't know so theoretically those flaws could have been exploited. That's my understanding of their major issue anyway.
Considering all the stuff the NSA has been caught doing over the years they don't really have any ground to complain.
Just watched this video from Gamers Nexus and found it an interesting summary of the situation. At least for me it was as i think I've reach saturation point on reading about the technical aspects.
http://www.tomshardware.co.uk/meltdown-spectre-malware-found-fortinet,news-57826.html We that's just dandy.
hmmm im in a middle of a but build strongly considering selling my gear and switching to threadripper
MeltdownPrime and SpectrePrime variants to add to the pool now. https://www.digitaltrends.com/computing/princeton-nvidia-prime-meltdown-spectre/amp/ Sounds like software patches will deal with them but, from how I read it, they'll need a different architecural solution to the one they need for Meltdown and Spectre.
