Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp8140276ybl; Thu, 16 Jan 2020 11:19:10 -0800 (PST) X-Google-Smtp-Source: APXvYqxkjoIIrPoB8uwjPLuFu7KzosAPsCMGpO70OtU/7bGY8Om76PqaIdjGVL92ePOA8y4S14Ct X-Received: by 2002:a9d:7b4a:: with SMTP id f10mr3421812oto.4.1579202350298; Thu, 16 Jan 2020 11:19:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579202350; cv=none; d=google.com; s=arc-20160816; b=n7T/BEj9gOJfsFGk1oF5fyk0DL1+3f79cdAdTf+AnI1AE1u3LmmMgtb9YPhe9m94u5 vJ1yhrgntmH9iX6KZAehyko85baqqZzsfT/VNuXzN3HNKSYMuA/2m2ytmHnHucv65JJg +Ig5RRZVV4m9pl0bkSw1XHFp4sNoX8Gm1yI5rKKU7nxINrNfyCWCSBYrD6Vkw5I3lgNG 1Yw+IJTcqQTupDmdIEiisFXjzj9P20Q60fnAnl/wdDWwaG+lDC/yIonsFC/YVlSCGhci vWfAPXWRN2axH4IlmiB+Rz79K5GvQovq2LPPfQZFbeAEtubURiNjMN9w7OH8t54jO7TP qEoA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=SJv8SzQEU6n/bmi4O3SBpkqFS0VQA+gST76SMeOeIUU=; b=GM/81AlDNzFcgFd/DDx9kSt7JM50FbZ5WlF+UiQozkVtImrKEq48+awAVfRYWwg+i3 LcI+ec8NBad7700MYpOddoqHjdPTkGe4jlI7sjs51JbJDvhgJWPjgGwxZK1b/TH0Ct4T Zh6p4KWCJkP9n00ncv83hrcBSGNG/sNtKTz1uo0VjK5afUmDelkYbl/nUnNFCeTNBjPv fXRzadfkDQymXFErnjsvHVA9RiGK5FMfiTraBucstuABAkKlZsnZ0FgA+iMoM4z8CxJC mc8vurY0JDlyLxXR/3ZSPO43Zkqr3o6+tNdhg6EzsEw5Pe9s5Wh5ViWZcdMAKbhmDG7F 9u4g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 65si333485oif.14.2020.01.16.11.18.57; Thu, 16 Jan 2020 11:19:10 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405059AbgAPTQf (ORCPT + 99 others); Thu, 16 Jan 2020 14:16:35 -0500 Received: from mga11.intel.com ([192.55.52.93]:50650 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733204AbgAPTQd (ORCPT ); Thu, 16 Jan 2020 14:16:33 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2020 11:16:32 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,327,1574150400"; d="scan'208";a="373426824" Received: from otc-nc-03.jf.intel.com (HELO otc-nc-03) ([10.54.39.25]) by orsmga004.jf.intel.com with ESMTP; 16 Jan 2020 11:16:32 -0800 Date: Thu, 16 Jan 2020 11:16:32 -0800 From: "Raj, Ashok" To: Jari Ruusu Cc: Linus Torvalds , Andy Lutomirski , Luis Chamberlain , Borislav Petkov , Fenghua Yu , johannes.berg@intel.com, Linux Kernel Mailing List , stable , Hans de Goede , Andy Lutomirski , Ashok Raj Subject: Re: Fix built-in early-load Intel microcode alignment Message-ID: <20200116191632.GB117689@otc-nc-03> References: <5C216684-6FDF-41B5-9F51-89DC295F6DDC@amacapital.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jari Sorry for the delay, just returned after a long vacation. On Thu, Jan 16, 2020 at 08:55:52AM +0200, Jari Ruusu wrote: > On 1/15/20, Linus Torvalds wrote: > > However, the most likely cause is that you have a borderline dodgy > > system, and the microcode update then just triggers a pre-existing > > problem. > > For that particular processor model, there appears to be microcode > updates for four steppings: 9 10 11 and 12. My model is stepping > 9, so it appears to be early commercially sold version of that > model. Probably more problems on it than on later steppings. I don't suspect the alignment issue during microcode load to trigger any hangs after couple days. Its only used to copy to some internal store. So once the ucode is loaded and if you look at /proc/cpuinfo and it reflects the latest microcode you are past the alignment issue. I suspect its something else. Can you please also document the OEM, BIOS versions, and also both the old and new microcode versions after the update. Would suggest logging the hang issue in public github for microcode issues. This would let the product folks look at them. https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files > > > But it might be worth it if the intel people could check up with their > > microcode people on this anyway - if there is _one_ report of "my > > system locks up with newer ucode", that's one thing. But if Jari isn't > > alone... > Cheers, Ashok