rpms/kexec-tools
7
0
Fork 0
Code Issues Pull Requests Releases Activity

doc/kdump.conf: properly format list

Browse Source 
man files doesn't preserve line breaks. Construct a list to list the
cases where additional memory will be reserved.

Fixes: c752cbb2 ("Explain the auto_reset_crashkernel option in more details")
Reported-by: Jie Li <jieli@redhat.com>
Signed-off-by: Coiby Xu <coxu@redhat.com>
Reviewed-by: Philipp Rudo <prudo@redhat.com>
This commit is contained in:
Coiby Xu 2024-03-13 14:18:24 +08:00 committed by Lichen Liu
parent 13caec13ae
commit 172fe23577
No known key found for this signature in database
GPG Key ID: 2ED8215EF57B3D6C
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
kdump.conf.5
View File

@ -32,17 +32,22 @@ determine whether to reset kernel crashkernel parameter to the default value
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)
.IP
\- AMD Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV)
.IP
\- Mellanox 5th generation network driver
.IP
\- aarch64 64k kernel
.IP
\- Firmware-assisted dump (FADump)
.PP
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).
.PP
.RE
.B raw <partition>