linux-kernel - Re: 4.15.17 regression: bisected: timeout during microcode update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180419123217.GA19746@araj-mobl1.jf.intel.com>
Date:   Thu, 19 Apr 2018 05:32:18 -0700
From:   "Raj, Ashok" <ashok.raj@...el.com>
To:     Borislav Petkov <bp@...e.de>
Cc:     Vitezslav Samel <vitezslav@...el.cz>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, Ashok Raj <ashok.raj@...el.com>
Subject: Re: 4.15.17 regression: bisected: timeout during microcode update

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...