Hi, On Mon, Sep 20, 2021 at 02:56:15AM +0200, Mike Galbraith wrote: > On Sun, 2021-09-19 at 20:04 +0300, Mike Rapoport wrote: > > > > Can you please send the boot log of a working kernel up to > > > > "Memory: %luK/%luK available" > > > > line for both of them? > > Desktop box: > [ 0.000000] microcode: microcode updated early to revision 0x28, date = 2019-11-12 > [ 0.000000] Linux version 5.15.0.g02770d1-tip (root@homer) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils; SUSE Linux Enterprise 15) 2.35.1.20201123-7.18) #46 SMP Sun Sep 19 18:42:41 CEST 2021 > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0.g02770d1-tip root=UUID=891c2a1f-cc1a-464b-a529-ab6add65aa21 scsi_mod.use_blk_mq=1 ftrace_dump_on_oops skew_tick=1 nortsched nodelayacct audit=0 cgroup_disable=memory cgroup_hide=all mitigations=off noresume panic=60 ignore_loglevel showopts crashkernel=204M Thanks! Can't say anything caught my eye, except the early microcode update. Just to rule that out, can you try booting without the early microcode update? And, to check Juergen's suggestion about failure in memblock_x86_reserve_range_setup_data(), can you try this patch on top of the failing tip: diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index 25425edc81a4..78162d9e90cf 100644 --- a/arch/x86/kernel/setup.c +++ b/arch/x86/kernel/setup.c @@ -716,8 +716,6 @@ static void __init early_reserve_memory(void) if (efi_enabled(EFI_BOOT)) efi_memblock_x86_reserve_range(); - memblock_x86_reserve_range_setup_data(); - reserve_ibft_region(); reserve_bios_regions(); trim_snb_memory(); @@ -888,6 +886,8 @@ void __init setup_arch(char **cmdline_p) */ x86_configure_nx(); + memblock_x86_reserve_range_setup_data(); + parse_early_param(); #ifdef CONFIG_MEMORY_HOTPLUG -- Sincerely yours, Mike.
