[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190608100139.GC26148@MiWiFi-R3L-srv>
Date: Sat, 8 Jun 2019 18:01:39 +0800
From: Baoquan He <bhe@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: lijiang <lijiang@...hat.com>, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, tglx@...utronix.de, mingo@...hat.com,
akpm@...ux-foundation.org, dave.hansen@...ux.intel.com,
luto@...nel.org, peterz@...radead.org, x86@...nel.org,
hpa@...or.com, dyoung@...hat.com, Thomas.Lendacky@....com
Subject: Re: [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel
e820 table
On 06/08/19 at 11:10am, Borislav Petkov wrote:
> On Sat, Jun 08, 2019 at 11:54:51AM +0800, Baoquan He wrote:
> > Is it a UEFI box?
>
> Yes.
OK, it doesn't matter with uefi since CONFIG_RANDOMIZE_BASE is not set.
>
> > If it's uefi machine, it should relate to below issue. Because kexec
> > always fails to randomly choose a new position for kernel.
>
> The kernel succeeds in selecting a position for the kernel - the kexec
> kernel doesn't load when a panic happens. Rather, the box panics and
> nothing more.
OK, it may be different with the case we met, if panic happened when
load a kdump kernel.
We can load with 'kexec -l' or 'kexec -p', but can't boot after triggering
crash or execute 'kexec -e' to do kexec jumping.
Powered by blists - more mailing lists