From: Hugh Dickins <hughd@google.com>
To: Borislav Petkov <bp@suse.de>
Cc: Dan Williams <dan.j.williams@intel.com>,
Anjaneya Chagam <ajaneya.chagam@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: 5.16-rc: "x86/boot: Pull up cmdline" breaks mem=
Date: Wed, 8 Dec 2021 21:44:54 -0800 (PST) [thread overview]
Message-ID: <ae2bb14d-d27a-e76d-adde-ef888d373343@google.com> (raw)
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".
I have not tried 5.15-stable, but guess that is likewise afflicted.
Sympathy, but no suggestions from me: early init ordering is hard!
Hugh
next reply other threads:[~2021-12-09 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 5:44 Hugh Dickins [this message]
2021-12-09 5:49 ` 5.16-rc: "x86/boot: Pull up cmdline" breaks mem= Hugh Dickins
2021-12-09 10:03 ` Borislav Petkov
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=ae2bb14d-d27a-e76d-adde-ef888d373343@google.com \
--to=hughd@google.com \
--cc=ajaneya.chagam@intel.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.