From: Juergen Gross <jgross@suse.com>
To: Mike Galbraith <efault@gmx.de>, Mike Rapoport <rppt@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
marmarek@invisiblethingslab.com, Borislav Petkov <bp@suse.de>,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/setup: Call early_reserve_memory() earlier
Date: Mon, 20 Sep 2021 13:33:06 +0200 [thread overview]
Message-ID: <6499cba1-1f86-f793-a3a7-815a71296249@suse.com> (raw)
In-Reply-To: <65a61ffdb4c8090320ec98fe5004e6f7808fa4b9.camel@gmx.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 684 bytes --]
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
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-09-20 11:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 9:41 [PATCH] x86/setup: call early_reserve_memory() earlier Juergen Gross
2021-09-14 10:03 ` Jan Beulich
2021-09-14 11:06 ` Juergen Gross
2021-09-15 11:00 ` Borislav Petkov
2021-09-16 9:09 ` Mike Rapoport
2021-09-16 10:29 ` Borislav Petkov
2021-09-16 10:31 ` Juergen Gross
2021-09-14 10:49 ` Marek Marczykowski-Górecki
2021-09-16 10:50 ` [tip: x86/urgent] x86/setup: Call " tip-bot2 for Juergen Gross
2021-09-19 16:55 ` Mike Galbraith
2021-09-19 17:04 ` Mike Rapoport
2021-09-20 0:56 ` Mike Galbraith
2021-09-20 9:26 ` Mike Rapoport
2021-09-20 9:38 ` Borislav Petkov
2021-09-20 11:25 ` Mike Galbraith
2021-09-20 11:33 ` Juergen Gross [this message]
2021-09-19 17:15 ` Borislav Petkov
2021-09-20 6:00 ` Juergen Gross
2021-09-20 9:46 ` Mike Rapoport
2021-09-20 22:48 ` Nathan Chancellor
2021-09-21 3:38 ` Borislav Petkov
2021-09-21 3:59 ` Nathan Chancellor
2021-09-21 7:36 ` Borislav Petkov
2021-09-20 12:04 [PATCH v2] x86/setup: call " Juergen Gross
2021-09-22 17:18 ` [tip: x86/urgent] x86/setup: Call " tip-bot2 for Juergen Gross
2021-11-04 5:38 ` Williams, Dan J
2021-11-04 11:40 ` Borislav Petkov
2021-11-04 17:36 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6499cba1-1f86-f793-a3a7-815a71296249@suse.com \
--to=jgross@suse.com \
--cc=bp@suse.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=rppt@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).