From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751204AbdL3RsN (ORCPT ); Sat, 30 Dec 2017 12:48:13 -0500 Received: from lb1.openmailbox.org ([5.79.108.160]:34721 "EHLO mta-1.openmailbox.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751002AbdL3RsM (ORCPT ); Sat, 30 Dec 2017 12:48:12 -0500 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Subject: Re: [tip:x86/urgent] x86/microcode/intel: Disable late loading on model 79 From: sonofagun@openmailbox.org Date: Sat, 30 Dec 2017 17:38:58 -0000 User-Agent: OpenMailBox Webmail To: linux-kernel@vger.kernel.org Message-Id: <20171230173858.B92184E0022@mta-1.openmailbox.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id vBUHmKdR019762 I suppose it is for Broadwell EX(Expandable or Expensive, whichever you like). The patch description is wrong! Document 334165-010US describes erratum BDF90: Loading Microcode Updates or Executing an Authenticated Code Module May Result in a System Hang I have not read such a bug in the past. I only knew that AMD K7 could not get microcode updates at all. Broadwell EX must not have their microcode updated because loading it will cause an UE if the microcode has signature less than 0x0b000021. I will check what is the signature of the latest update supplied by intel for this model just out of curiosity. This patch does not check microcode signature, it disables all updates. Is that intentional?