The documentation talks about rebuilding the initramfs image after partition migration. While it is implicit that a kdump reload is needed after initramfs image is built, mention that explicitly to avoid missing that step inadvertently.

As initramfs image rebuild is needed for fadump as well, add the steps for the same under fadump-howto.txt.

Signed-off-by: Hari Bathini hbathini@linux.ibm.com --- fadump-howto.txt | 17 +++++++++++++++++ kexec-kdump-howto.txt | 4 ++++ 2 files changed, 21 insertions(+)

diff --git a/fadump-howto.txt b/fadump-howto.txt index 433e9a6..0eeba42 100644 --- a/fadump-howto.txt +++ b/fadump-howto.txt @@ -171,6 +171,23 @@ perform postmortem analysis:

and so on...

+ +Notes on fadump +=============== + +To save memory usage and disk space, the initramfs is generated strictly +against the system it will run on, and contains the minimum set of kernel +modules and utilities for dump capture. + +With kdump service enabled, kdumpctl will try to detect possible system +change and rebuild the initramfs if needed. But it can not guarantee to +cover every possible case. So after a hardware change, disk migration, +storage setup update or any similar system level changes, it's highly +recommended to rebuild the initramfs manually with following command: + + # kdumpctl rebuild + + Saving vmcore-dmesg.txt ----------------------- Kernel log bufferes are one of the most important information available diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt index 88af607..bb9c221 100644 --- a/kexec-kdump-howto.txt +++ b/kexec-kdump-howto.txt @@ -163,6 +163,10 @@ recommended to rebuild the initramfs manually with following command:

# kdumpctl rebuild

+and run reload to ensure rebuilt initramfs is used while loading kdump: + + # kdumpctl reload +

Saving vmcore-dmesg.txt =======================