From: Mike Rapoport <rppt@kernel.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@intel.com>,
Ingo Molnar <mingo@kernel.org>,
regressions@lists.linux.dev,
Song Shuai <songshuaishuai@tinylab.org>
Subject: Re: [REGRESSION] Platforms supporting SGX fail to kexec due to 96c6b8f212a ("memblock: report failures when memblock_can_resize is not set")
Date: Sun, 31 Dec 2023 09:26:22 +0200 [thread overview]
Message-ID: <ZZEXnl3w0K6avYR3@kernel.org> (raw)
In-Reply-To: <ZY4T7YxrJZCxhMxx@a4bf019067fa.jf.intel.com>
Hi,
On Thu, Dec 28, 2023 at 04:33:49PM -0800, Ashok Raj wrote:
> Hi
>
> 96c6b8f212a ("memblock: report failures when memblock_can_resize is not set")
>
> Causes kexec failure. Backing out this change, kexec succeeds. Symptom is
> it appears to hang, possibly hung at the panic. Although I have the
> earlyprintk enabled, I don't see any console messages when new kernel
> boots.
>
> Also tested turning off CONFIG_X86_SGX, the kernel with this commit
> included also kexec's fine.
>
> Booting from warm/cold reset has no issues. Only kexec to new kernel with
> this change included and CONFIG_X86_SGX=y causes the kexec failure.
Can you add memblock=debug to the kernel command line and send logs for
normal boot and kexec with CONFIG_X86_SGX=y and e96c6b8f212a reverted?
> #regzbot introduced: 96c6b8f212a
> --
> Cheers,
> Ashok
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-12-31 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 0:33 [REGRESSION] Platforms supporting SGX fail to kexec due to 96c6b8f212a ("memblock: report failures when memblock_can_resize is not set") Ashok Raj
2023-12-30 9:48 ` Borislav Petkov
2023-12-31 7:26 ` Mike Rapoport [this message]
2024-02-01 10:38 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-01 18:36 ` Ashok Raj
2024-01-03 11:06 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZZEXnl3w0K6avYR3@kernel.org \
--to=rppt@kernel.org \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=songshuaishuai@tinylab.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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