From owner-freebsd-questions@freebsd.org Sat Feb 3 16:40:07 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D38D2EDA023 for ; Sat, 3 Feb 2018 16:40:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7200970F64 for ; Sat, 3 Feb 2018 16:40:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1ei0rG-000259-AH; Sat, 03 Feb 2018 17:40:06 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id w13GbNLB004307 for ; Sat, 3 Feb 2018 17:37:23 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id w13GbNvt004306 for freebsd-questions@freebsd.org; Sat, 3 Feb 2018 17:37:23 +0100 (CET) (envelope-from news) To: freebsd-questions@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.questions Subject: Re: Response to Meltdown and Spectre Date: Sat, 3 Feb 2018 16:37:23 -0000 (UTC) Message-ID: References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> User-Agent: slrn/1.0.3 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2018 16:40:08 -0000 On 2018-02-02, Paul Pathiakis via freebsd-questions 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. -- Christian "naddy" Weisgerber naddy@mips.inka.de