Hi,
Recently I experienced a kernel panic which is related to efa module
when testing kexec -l && kexec -e to switch to a new kernel on AWS
i4g.16xlarge instance.
Here is the dmesg log:
[6.379918] systemd[1]: Mounting FUSE Control File System...
[6.381984] systemd[1]: Mounting Kernel Con
There are regression reports[1][2] that crashkernel region on x86_64 can't
be added into iomem tree sometime. This causes the later failure of kdump
loading.
This happened after commit 4a693ce65b18 ("kdump: defer the insertion of
crashkernel resources") was merged.
Even though, these reported iss
On 03/24/24 at 11:27am, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > On 03/24/24 at 05:06am, Ingo Molnar wrote:
> > >
> > > * Baoquan He wrote:
> > >
> > ..snip
> > > > ---
> > > > arch/x86/include/asm/crash_reserve.h | 2 ++
> > > > kernel/crash_reserve.c | 7 +++
>
Hello,
On 3/18/2024 11:00 PM, Dave Young wrote:
Hi,
Added Ard in cc.
On 03/18/24 at 07:02am, Ashish Kalra wrote:
From: Ashish Kalra
For kexec use case, need to use and stick to the EFI memmap passed
from the first kernel via boot-params/setup data, hence,
skip efi_arch_mem_reserve() during
* Baoquan He wrote:
> On 03/24/24 at 05:06am, Ingo Molnar wrote:
> >
> > * Baoquan He wrote:
> >
> ..snip
> > > ---
> > > arch/x86/include/asm/crash_reserve.h | 2 ++
> > > kernel/crash_reserve.c | 7 +++
> > > 2 files changed, 9 insertions(+)
> > >
> > > diff --git a
On 03/24/24 at 05:06am, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
..snip
> > ---
> > arch/x86/include/asm/crash_reserve.h | 2 ++
> > kernel/crash_reserve.c | 7 +++
> > 2 files changed, 9 insertions(+)
> >
> > diff --git a/arch/x86/include/asm/crash_reserve.h
> > b/a