Explain the auto_reset_crashkernel option in more details

Resolves: https://issues.redhat.com/browse/RHEL-17451
Upstream: Fedora
Conflict: None

commit c752cbb2d393c9ae27475f184e2933ff65be50b1
Author: Coiby Xu <coxu@redhat.com>
Date:   Wed Dec 6 16:15:50 2023 +0800

    Explain the auto_reset_crashkernel option in more details

    Resolves: https://issues.redhat.com/browse/RHEL-17451

    Explain what factors affect the default crashkernel value and ask users
    to reset it manually if needed.

    Cc: Baoquan He <bhe@redhat.com>
    Cc: Jie Li <jieli@redhat.com>
    Acked-by: Baoquan He <bhe@redhat.com>
    Signed-off-by: Coiby Xu <coxu@redhat.com>

Signed-off-by: Coiby Xu <coxu@redhat.com>
This commit is contained in:
Coiby Xu 2023-12-25 10:51:41 +08:00 committed by Tao Liu
parent c179f45e05
commit 83698d84aa
1 changed files with 14 additions and 1 deletions

View File

@ -29,7 +29,20 @@ understand how this configuration file affects the behavior of kdump.
.B auto_reset_crashkernel <yes|no>
.RS
determine whether to reset kernel crashkernel parameter to the default value
or not when kexec-tools is updated or a new kernel is installed.
or not when kexec-tools is updated or a new kernel is installed. The default
crashkernel values are different for different architectures and also take the
following factors into consideration,
- AMD Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV)
- Mellanox 5th generation network driver
- aarch64 64k kernel
- Firmware-assisted dump (FADump)
Since the kernel crasherkernel parameter will be only reset when kexec-tools is
updated or a new kernel is installed, you need to call "kdumpctl
reset-crashkernel [--kernel=path_to_kernel]" if you want to use the default
value set after having enabled features like SME/SEV for a specific kernel. And
you should also reboot the system for the new crashkernel value to take effect.
Also see kdumpctl(8).
.B raw <partition>
.RS