Boots successfully with "noefi" kernel parameter :) On Fri, Jan 5, 2018 at 12:43 PM, Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > >> On Jan 5, 2018, at 9:14 AM, Pavel Tatashin <pasha.tatashin@xxxxxxxxxx> wrote: >> >> Hi Andy, >> >> This is bare metal, not VM, read my other email in this thread about >> the machine on which I am testing. Sometime hang happens a little >> later: >> >> [ 5.088948] microcode: CPU36 sig=0x406f1, pf=0x1, revision=0xb00001d >> [ 5.096076] microcode: CPU37 sig=0x406f1, pf=0x1, revision=0xb00001d >> [ 5.103206] microcode: CPU38 sig=0x406f1, pf=0x1, revision=0xb00001d >> [ 5.110326] microcode: CPU39 sig=0x406f1, pf=0x1, revision=0xb00001d >> [ 5.117467] microcode: Microcode Update Driver: v2.01 >> <tigran@xxxxxxxxxxxxxxxxxxxx>, Peter Oruba >> [ 5.127476] registered taskstats version 1 >> [ 5.132058] Loading compiled-in X.509 certificates >> [ 5.138206] Loaded X.509 cert 'Build time autogenerated kernel key: >> 26871d9e2c53359981a91797284d4f630796d8cf' >> [ 5.149337] zswap: loaded using pool lzo/zbud >> [ 5.154215] page_owner is disabled >> [ 5.161468] Key type trusted registered >> [ 5.169226] Key type encrypted registered >> [ 5.173719] ima: No TPM chip found, activating TPM-bypass! >> [ 5.179918] evm: HMAC attrs: 0x1 >> [ 5.184958] rtc_cmos 00:00: setting system clock to 2018-01-05 >> 15:40:45 UTC (1515166845) >> [ 5.196099] Freeing unused kernel memory: 1856K >> <hang / reboot here> > > Gah, too many emails. > > Someone probably just needs to look at the EFI think code. Does it boot if you disable EFI support in the kernel (noefi boot option, I think, or maybe just compile it out. > > > >> >> Thank you, >> Pavel