From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2D056C33CB3 for ; Thu, 16 Jan 2020 19:16:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 12BB42073A for ; Thu, 16 Jan 2020 19:16:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733240AbgAPTQe (ORCPT ); Thu, 16 Jan 2020 14:16:34 -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: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@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