linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Sun, 15 May 2016 14:16:28 +0200
From:	Jim Bos <jim876@...all.nl>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	Borislav Petkov <bp@...e.de>, Thomas Gleixner <tglx@...utronix.de>
Subject: Builtin early microcode breaks s2ram v4.6-rcX

As I noticed microcode was no longer being loaded on v4.6-rcX I switched
to builtin microcode as described in

  Documentation/x86/early-microcode.txt

So I have now this:
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-2a-07 radeon/REDWOOD_me.bin
radeon/REDWOOD_pfp.bin radeon/REDWOOD_rlc.bin radeon/REDWOOD_smc.bin
radeon/CYPRESS_uvd.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set

That works, i.e. when booting as very first line I get message microcode
is loaded, see attached dmesg

However, after suspend to ram, trying to resume results in total lockup
of the machine:  no ping,  no sysrq-keys, only hard reset works.

Trying to bisect this didn't really work, earlier kernel (v4.5) doesn't
even boot with this config.

I'm seeing this on 2 rather different machines, on intel quadcore on 2-3
year old mobo and a dual core pentium on fairly new mobo.
Note that both machines do boot using EFI.

_
Jim

Download attachment "dmesg.gz" of type "application/gzip" (15407 bytes)