From: Borislav Petkov <bp@alien8.de>
To: Hugh Dickins <hughd@google.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Anjaneya Chagam <anjaneya.chagam@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Mike Rapoport <rppt@kernel.org>
Subject: Re: 5.16-rc: "x86/boot: Pull up cmdline" breaks mem=
Date: Thu, 9 Dec 2021 11:03:07 +0100 [thread overview]
Message-ID: <YbHUW1KTfvJtxNwP@zn.tnic> (raw)
In-Reply-To: <ae2bb14d-d27a-e76d-adde-ef888d373343@google.com>
Hi Hugh,
On Wed, Dec 08, 2021 at 09:44:54PM -0800, Hugh Dickins wrote:
> Bad news, I'm afraid: I boot with "mem=1G" on the cmdline for testing,
> which worked fine on 5.16-rc1, but does not work on 5.16-rc2 onwards.
>
> Bisection arrived at 8d48bf8206f7 ("x86/boot: Pull up cmdline preparation
> and early param parsing"); and reverting c0f2077baa41 ("x86/boot: Mark
> prepare_command_line() __init") then 8d48bf820cf7 does fix my "mem=1G".
Yeah, I had a bug reporter report breaking on his machine but he didn't
respond to my request for additional details.
Can you pls send me full dmesg and .config of the -rc1 kernel which
still boots fine. I'd like to try to repro.
> I have not tried 5.15-stable, but guess that is likewise afflicted.
Right.
> Sympathy, but no suggestions from me: early init ordering is hard!
Tell me about it! This is the 4 or so "fix" which tries to address
fallout from Mike and mine's attempt to sort out memblock ordering
during early boot.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-12-09 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 5:44 5.16-rc: "x86/boot: Pull up cmdline" breaks mem= Hugh Dickins
2021-12-09 5:49 ` Hugh Dickins
2021-12-09 10:03 ` Borislav Petkov [this message]
2021-12-09 12:49 ` Borislav Petkov
2021-12-09 17:25 ` Hugh Dickins
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=YbHUW1KTfvJtxNwP@zn.tnic \
--to=bp@alien8.de \
--cc=anjaneya.chagam@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@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