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]

Date:   Fri, 20 Apr 2018 11:52:20 +0200
From:   Borislav Petkov <bp@...e.de>
To:     Vitezslav Samel <vitezslav@...el.cz>
Cc:     "Raj, Ashok" <ashok.raj@...el.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: 4.15.17 regression: bisected: timeout during microcode update

On Fri, Apr 20, 2018 at 08:20:21AM +0200, Vitezslav Samel wrote:
>   ;-)  This time it works.

Good. :-)

> microcode: __reload_late: CPU1 waiting to exit
> x86/CPU: CPU features have changed after loading microcode, but might not take effect.
> x86/CPU: Please consider either early loading through initrd/built-in or a potential BIOS update.
> ------------------------------------------------------

Ok, and after this happens

$ grep microcode /proc/cpuinfo | uniq

shows only 0x24, correct?

> 	Thank you very much,

No, thank you for reporting and testing!

Ok, cleaned up patches with commit messages coming up.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--