Received-SPF: pass (google.com: domain of linux-kernel+bounces-13647-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Sun, 31 Dec 2023 09:26:22 +0200
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")
Message-ID: <ZZEXnl3w0K6avYR3@kernel.org>
References: <ZY4T7YxrJZCxhMxx@a4bf019067fa.jf.intel.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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.