[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZZEXnl3w0K6avYR3@kernel.org>
Date: Sun, 31 Dec 2023 09:26:22 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Ashok Raj <ashok.raj@...el.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
LKML Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>,
Ingo Molnar <mingo@...nel.org>, regressions@...ts.linux.dev,
Song Shuai <songshuaishuai@...ylab.org>
Subject: Re: [REGRESSION] Platforms supporting SGX fail to kexec due to
96c6b8f212a ("memblock: report failures when memblock_can_resize is not
set")
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.
Powered by blists - more mailing lists