On 12/19/2016 01:07 PM, Borislav Petkov wrote: > On Mon, Dec 19, 2016 at 05:40:27PM +0100, Borislav Petkov wrote: >> On Mon, Dec 19, 2016 at 11:10:29AM -0500, Boris Ostrovsky wrote: >>> config attached. I'll see how I can get you the initrd. >> Wait a bit, lemme see if I can repro with my initrd here. > Hmm, it boots here (btw, this is with the 4 patches applied). > > [ 0.000000] Linux version 4.9.0upstream-11409-gf3302378ed83-dirty > (boris@pd) (gcc version 6.2.1 20161124 (Debian 6.2.1-5) ) #1 SMP Mon Dec 19 > 18:50:17 CET 2016 > [ 0.000000] x86/fpu: Legacy x87 FPU detected. > [ 0.000000] e820: BIOS-provided physical RAM map: > ... > [ 0.000000] RAMDISK: [mem 0x37845000-0x37c19fff] > [ 0.000000] Allocated new RAMDISK: [mem 0x36470000-0x36844f5e] > [ 0.000000] Move RAMDISK from [mem 0x37845000-0x37c19f5e] to [mem > 0x36470000-0x36844f5e] > ... > [ 0.243326] smpboot: CPU0: AMD E-350 Processor (family: 0x14, model: 0x1, > stepping: 0x0)
IIUIC find_microcode_in_initrd() is called with paging on only on Intel (which is where I observed it). > [ 0.243637] Performance Events: AMD PMU driver. > ... > [ 1.307957] microcode: microcode updated early to new > patch_level=0x05000029 > [ 1.308212] microcode: CPU0: patch_level=0x05000029 > [ 1.308374] microcode: CPU1: patch_level=0x05000029 > [ 1.308726] microcode: Microcode Update Driver: v2.2. > > $ uname -a > Linux x1 4.9.0upstream-11409-gf3302378ed83-dirty #1 SMP Mon Dec 19 18:50:17 > CET 2016 i686 GNU/Linux > > So I guess I wanna take a look at the initrd now... It'll have to wait until (my) evening, I'll ping you then. -boris