Date: Sat, 3 Feb 2018 17:30:10 -0500 From: Paul Pathiakis <pathiaki2@yahoo.com> To: freebsd-questions@freebsd.org Subject: Re: Response to Meltdown and Spectre Message-ID: <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> In-Reply-To: <slrnp7bpa3.2k8.naddy@lorvorc.mips.inka.de> References: <CY1PR01MB12472D916F78A638731ECCE68FFB0@CY1PR01MB1247.prod.exchangelabs.com> <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <CA%2BtpaK2o1nbY2W2JVRtogN=P2VM9rag_dodK=GtLWgKwNsYZkg@mail.gmail.com> <F395799E-2C94-47E9-AA1C-5CB075C50076@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> <slrnp7bpa3.2k8.naddy@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
http://www.zdnet.com/article/meltdown-spectre-firmware-glitch-intel-warns-of-risk-of-sudden-reboots/ The sudden reboots and non-starts have been tracked to the patch. On 2/3/2018 11:37 AM, Christian Weisgerber wrote: > On 2018-02-02, Paul Pathiakis via freebsd-questions <freebsd-questions@freebsd.org> wrote: > >> Intels patches have 'bricked' processors. Yes, made them totally >> unusable as they rushed them out the door. They pulled them immediately >> and told people to destroy them. > That is wildly exaggerated. I'm running several machines with the > microcode updates that Intel later pulled--in fact I'm typing this > on one of them--and nothing has been bricked. Intel is extremely > coy with details, but it stands to reason that the reliability > problems that caused them to retract the microcode will only appear > when the operating system actually uses the newly introduced > IBRS/IBPB/STIBP features. > --- This email has been checked for viruses by AVG. http://www.avg.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0520dd84-c00c-fbf2-da1c-f6ff4c63739d>