linux-kernel - Re: Builtin early microcode breaks s2ram v4.6-rcX

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: <e8d795f4-00a5-a0e2-9874-bc87e068854d@xs4all.nl>
Date:	Sun, 15 May 2016 17:45:49 +0200
From:	Jim Bos <jim876@...all.nl>
To:	Borislav Petkov <bp@...e.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Builtin early microcode breaks s2ram v4.6-rcX

On 05/15/2016 04:48 PM, Borislav Petkov wrote:
> On Sun, May 15, 2016 at 02:16:28PM +0200, Jim Bos wrote:
>> However, after suspend to ram, trying to resume results in total
>> lockup of the machine: no ping, no sysrq-keys, only hard reset works.
> 
> Does it work when you add "dis_ucode_ldr" to the kernel command line?
> 

Yes,  it boots  / suspends  / resumes  just fine.
(but no microcode updates in dmesg)

Jim