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

Message-ID: <20180418081140.GA2439@pc11.op.pod.cz>
Date:   Wed, 18 Apr 2018 10:11:40 +0200
From:   Vitezslav Samel <vitezslav@...el.cz>
To:     Ashok Raj <ashok.raj@...el.com>, Borislav Petkov <bp@...e.de>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Subject: 4.15.17 regression: bisected: timeout during microcode update

	Hi!

  Starting with 4.15.17 I got panic "timeout during microcode update"
which I bisected down to commit 8e1161f94614 ("x86/microcode: Synchronize
late microcode loading") - upstream commit
a5321aec6412b20b5ad15db2d6b916c05349dbff.

  The panic happens during CPU microcode update.

  The same happens with 4.16+.

  Machine is "Supermicro X10SLM-F/X10SLM-F, BIOS 2.2 02/05/2015"
CPU is "Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz" with microcode
revision 0x1c. Microcode update files are in /lib/firmware/intel-ucode
(2018-03-12) - revision 0x24.

  I'm attaching .config and dmesg from 4.15.16 boot (known good).

  Could be done anything to prevent this panic?

	Cheers,

		Vita

View attachment ".config" of type "text/plain" (79804 bytes)

View attachment "dmesg-20180418-09:41-4.15.16" of type "text/plain" (40153 bytes)