[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c8eb9ed-8029-4e31-b957-083255b6616c@leemhuis.info>
Date: Wed, 3 Jan 2024 12:06:43 +0100
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: LKML Mailing List <linux-kernel@...r.kernel.org>,
regressions@...ts.linux.dev
Subject: Re: [REGRESSION] Platforms supporting SGX fail to kexec due to
96c6b8f212a ("memblock: report failures when memblock_can_resize is not set")
On 29.12.23 01:33, Ashok Raj wrote:
>
> 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.
>
> #regzbot introduced: 96c6b8f212a
Fix a typo and do a few other things while at it:
#regzbot introduced: e96c6b8f212a
#regzbot title: memblock: platforms supporting SGX fail to kexec
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Powered by blists - more mailing lists