On 12/19/23 at 01:31pm, Coiby Xu wrote:
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(a)redhat.com>
Cc: Jie Li <jieli(a)redhat.com>
Signed-off-by: Coiby Xu <coxu(a)redhat.com>
---
kdump.conf.5 | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/kdump.conf.5 b/kdump.conf.5
index 9117aa7b..0e6ff211 100644
--- a/kdump.conf.5
+++ b/kdump.conf.5
@@ -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
~~~ s/for/on/
Other than this minor concern, this looks good to me, thx.
Acked-by: Baoquan He <bhe(a)redhat.com>
+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
--
2.43.0