[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6499cba1-1f86-f793-a3a7-815a71296249@suse.com>
Date: Mon, 20 Sep 2021 13:33:06 +0200
From: Juergen Gross <jgross@...e.com>
To: Mike Galbraith <efault@....de>, Mike Rapoport <rppt@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
marmarek@...isiblethingslab.com, Borislav Petkov <bp@...e.de>,
stable@...r.kernel.org, x86@...nel.org
Subject: Re: [tip: x86/urgent] x86/setup: Call early_reserve_memory() earlier
On 20.09.21 13:25, Mike Galbraith wrote:
> On Mon, 2021-09-20 at 12:26 +0300, Mike Rapoport wrote:
>>
>> 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?
>
> Nogo.
>
>> 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:
>
> Yup, patchlet detoxified it for both boxen.
Yay!
Will respin my patch moving the call of early_reserve_memory() just
before the call of e820__memory_setup().
Thanks for reporting the issue and verifying my suspicion.
Juergen
Download attachment "OpenPGP_0xB0DE9DD628BF132F.asc" of type "application/pgp-keys" (3092 bytes)
Download attachment "OpenPGP_signature" of type "application/pgp-signature" (496 bytes)
Powered by blists - more mailing lists