Read more.Quote:
For now it is asking all its customers to hold off on applying Meltdown / Spectre updates.
Printable View
Read more.Quote:
For now it is asking all its customers to hold off on applying Meltdown / Spectre updates.
Can someone clarify, are the BIOS updates causing these problems the responsibility of Intel or the Mobo manufacturers?
I'm guessing Intel is providing the Microcode fix that then gets pushed out by the update and it's that bit that's causing the BSOD?
As I understand, Intel produces patches for various processor models / families and chipsets (Microcode). Then it hands these files off to motherboard and systems makers.Quote:
Originally Posted by Tabbykatze
In my case Gigabyte hasn't yet acted to supply a BIOS update for my Haswell desktop motherboard. However Dell produced a BIOS for my Haswell ultrabook - since been removed and the Nov 2017 release left in its place for users to roll back to.
That's the PCs, I have much less hope of a Spectre update coming from Google, via LG, for my 2015 flagship smartphone.
That's pretty much it as far as I can tell. Intel have done their bit (badly) supposedly by releasing the specific code and it's then up to the mobo manufacturers to stick it into an update for their particular mobos. Hence why, even though there may be a patch suited to your CPU, many mobos aren't getting patched, including mine. Apparently my 3 year old high end mobo that I spent a small fortune on isn't worthy, even though they have the code and just need to put it into a deployable BIOS update.Quote:
Originally Posted by Tabbykatze
It sounds like it's actually Intel's rushed out fix that is causing the issue. I suspect the BIOS update really is no more than allowing blind deployment of the Intel patch on the individual mobo infrastructure rather than any real integration into their own code so the blame for this debacle probably lays right at the feet of Intel.
I suspect that it's possible if you need legal recourse then you'd go to your mobo manufacturer who would then sue Intel for any losses they incurred.
*sings*
tralalalala Ryzen
Tralalalallaaaaa Threadripper
Gdam had constant reboots for days after the last udpate on my e5440 xeon -.-
I didn't think Android was at risk from Spectre as it requires low level assembly code and Android apps run in a VM?Quote:
Originally Posted by mtyson
Intel says it has identified patch issues causing reboots ... our coding guys suck !