Received: by 10.192.165.156 with SMTP id m28csp660043imm; Thu, 19 Apr 2018 05:34:11 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/cBPn6J0iAHTdkRFDasC0i/Zvq9hLimSLeK78/Mzy7c/n1wQR32OTaNqhmgnsdROAV+rz+ X-Received: by 10.101.98.153 with SMTP id f25mr5026319pgv.6.1524141251029; Thu, 19 Apr 2018 05:34:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524141250; cv=none; d=google.com; s=arc-20160816; b=UR5lVzeRorprZoRhEryD6vO0ANlw58JWkTtoWPZXknaBShCfsf7MBDc49D4YvnWX24 UM1SwjaKW3i+dT1xQ7uO4dBzO7lv7o4LIu0wMeQRq32dpsWFZvH34qo1Y/FOB1wIYStD K4ZVO6aKKJ0zBiaCW4M+IBxa+ZuL5y0HzFN5h6SLFvhxFwUHXCkV9s4xD0bXYZqZQ5qF HfoGfJgFYFOs3E1voqmh/7jXsED+EOw/Df2+uovQ47DSCibhHgFiMT9hpSUsBl/wvg9B 5IRy87kbl5cRGypvW1CR8Djy9VCfreDS8uGoigcxiXB636KWiVz++wnN5zN7AaXaV6Nq 8zYw== 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:arc-authentication-results; bh=KENZV2L16i/dWAPZsvVrKox053s2X7pWJGNdkQ1hS/Q=; b=JSJjWThAe0mU6ALU3O62mywoaapVOIpB2J7hlEd8unp08eyAJPlHiI7KTODNC/4Xap qKCbctanHXEOJvywCQKy3j90mtzF0dZ9ifhLIRHbQPSnPYfI0Fm7g7faZhK7AopVmPZR z/MBOEUhGIFCQqqAwCTf09WDNroUyFbXVeJ9syGX2n13mUlZDNnnEwWRqmJCV32CqTZN sImQWxHxrHooB1FdZ4AKOU8lMO0wswGL7mUsuX3e6jkyYt10/F5gNznbGjYMVN1VXR+K MRWlw+fKVKpX5dDO1djs+jxIyNpJEBMGLtKoov8qrimslDnH0AOKFr4xzevKkBssJHzg D5zg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i1-v6si3243464plt.178.2018.04.19.05.33.57; Thu, 19 Apr 2018 05:34:10 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752731AbeDSMcU (ORCPT + 99 others); Thu, 19 Apr 2018 08:32:20 -0400 Received: from mga17.intel.com ([192.55.52.151]:65294 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751565AbeDSMcT (ORCPT ); Thu, 19 Apr 2018 08:32:19 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Apr 2018 05:32:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,469,1517904000"; d="scan'208";a="35465898" Received: from araj-mobl1.jf.intel.com ([10.254.33.189]) by orsmga006.jf.intel.com with ESMTP; 19 Apr 2018 05:32:18 -0700 Date: Thu, 19 Apr 2018 05:32:18 -0700 From: "Raj, Ashok" To: Borislav Petkov Cc: Vitezslav Samel , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Ashok Raj Subject: Re: 4.15.17 regression: bisected: timeout during microcode update Message-ID: <20180419123217.GA19746@araj-mobl1.jf.intel.com> References: <20180418081140.GA2439@pc11.op.pod.cz> <20180418100721.GA5866@pd.tnic> <20180418120839.GA5655@pc11.op.pod.cz> <20180418122212.GA4290@pd.tnic> <20180418135330.GA23580@araj-mobl1.jf.intel.com> <20180419053531.GA2224@pc11.op.pod.cz> <20180419104829.GE3896@pd.tnic> <20180419120239.GA2377@pc11.op.pod.cz> <20180419121840.GF3896@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180419121840.GF3896@pd.tnic> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks.. also can you remove the ret below, and send the output of /proc/cpuinfo before and after? On Thu, Apr 19, 2018 at 02:18:41PM +0200, Borislav Petkov wrote: > } else { > + pr_info("%s: CPU%d returning 0x%x\n", __func__, cpu, err); > return ret; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > } > This should not panic, but curious what the microcode versions reported...