.editorconfig

@@ -0,0 +1,32 @@
+# EditorConfig configuration for kexec-tools
+# http://EditorConfig.org
+
+# Top-most EditorConfig file
+root = true
+
+# Default code style for kexec-tools scripts
+[*]
+end_of_line = lf
+shell_variant = posix
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = tab
+indent_size = 1
+switch_case_indent = false
+function_next_line = true
+binary_next_line   = false
+space_redirects    = true
+
+# Some scripts will only run with bash
+[{mkfadumprd,mkdumprd,kdumpctl,kdump-lib.sh}]
+shell_variant = bash
+
+# Use dracut code style for *-module-setup.sh
+[*-module-setup.sh,dracut-early-kdump.sh]
+shell_variant = bash
+indent_style = space
+indent_size = 4
+switch_case_indent = true
+function_next_line = false
+binary_next_line   = true
+space_redirects    = true

.gitignore

@@ -1,3 +1,24 @@
-SOURCES/1.7.2.tar.gz
-SOURCES/eppic_050615.tar.gz
-SOURCES/kexec-tools-2.0.26.tar.xz
+*.gz
+*.xz
+*.swp
+*.rpm
+/eppic_030413.tar.gz
+/makedumpfile-1.5.7.tar.gz
+/kexec-tools-2.0.8.tar.xz
+/kdump-anaconda-addon-005-2-g86366ae.tar.gz
+/kdump-anaconda-addon-005-5-gbf53665.tar.gz
+/kdump-anaconda-addon-005-8-ge6ea581.tar.gz
+/kdump-anaconda-addon-005-9-g6115ca7.tar.gz
+/kexec-tools-2.0.9.tar.xz
+/makedumpfile-1.5.8.tar.gz
+/eppic_050615.tar.gz
+/kexec-tools-2.0.10.tar.xz
+/kdump-anaconda-addon-005-10-gd16915f.tar.gz
+/kdump-anaconda-addon-005-11-g59f9b73.tar.gz
+/kdump-anaconda-addon-005-12-g60fa4c1.tar.gz
+/kdump-anaconda-addon-005-14-g563e904.tar.gz
+/kdump-anaconda-addon-005-16-g586cc82.tar.gz
+/kexec-tools-2.0.11.tar.xz
+/makedumpfile-1.5.9.tar.gz
+/kexec-tools-2.0.12.tar.xz
+coverage/

.kexec-tools.metadata

@@ -1,3 +0,0 @@
-24bce02cd42cdbb960ada4d9e733355582e35784 SOURCES/1.7.2.tar.gz
-a096c8e0892b559f40b01916aae240652f75b68a SOURCES/eppic_050615.tar.gz
-27cea5d032ec1e93506b8110222420abf754df2d SOURCES/kexec-tools-2.0.26.tar.xz

.packit.yaml

@@ -0,0 +1,16 @@
+# See the documentation for more information:
+# https://packit.dev/docs/configuration/
+
+specfile_path: kexec-tools.spec
+
+# add or remove files that should be synced
+files_to_sync:
+    - kexec-tools.spec
+    - .packit.yaml
+
+# name in upstream package repository or registry (e.g. in PyPI)
+upstream_package_name: kexec-tools
+# downstream (Fedora) RPM package name
+downstream_package_name: kexec-tools
+
+upstream_tag_template: v{version}

README

@@ -0,0 +1,12 @@
+Adding a patch to kexec-tools
+=============================
+There is a mailing list kexec@lists.fedoraproject.org where all the dicussion
+related to fedora kexec-tools happen. All the patches are posted there for
+inclusion and committed to kexec-tools after review.
+
+So if you want your patches to be included in fedora kexec-tools package,
+post these to kexec@lists.fedoraproject.org.
+
+One can subscribe to list and browse through archives here.
+
+https://admin.fedoraproject.org/mailman/listinfo/kexec

README.packit

@@ -0,0 +1,3 @@
+This repository is maintained by packit.
+https://packit.dev/
+The file was generated using packit 0.89.0.

SOURCES/60-kdump.install

@@ -1,36 +0,0 @@
-#!/usr/bin/bash
-
-COMMAND="$1"
-KERNEL_VERSION="$2"
-KDUMP_INITRD_DIR_ABS="$3"
-KERNEL_IMAGE="$4"
-
-if ! [[ ${KERNEL_INSTALL_MACHINE_ID-x} ]]; then
-    exit 0
-fi
-
-if [[ -d "$KDUMP_INITRD_DIR_ABS" ]]; then
-    KDUMP_INITRD="initrdkdump"
-else
-    # If `KDUMP_BOOTDIR` is not writable, then the kdump
-    # initrd must have been placed at `/var/lib/kdump`
-    if [[ ! -w "/boot" ]]; then
-        KDUMP_INITRD_DIR_ABS="/var/lib/kdump"
-    else
-        KDUMP_INITRD_DIR_ABS="/boot"
-    fi
-    KDUMP_INITRD="initramfs-${KERNEL_VERSION}kdump.img"
-fi
-
-ret=0
-case "$COMMAND" in
-    add)
-        # Do nothing, kdump initramfs is strictly host only
-        # and managed by kdump service
-        ;;
-    remove)
-        rm -f -- "$KDUMP_INITRD_DIR_ABS/$KDUMP_INITRD"
-        ret=$?
-        ;;
-esac
-exit $ret

SOURCES/98-kexec.rules

@@ -1,16 +0,0 @@
-SUBSYSTEM=="cpu", ACTION=="add", GOTO="kdump_reload"
-SUBSYSTEM=="cpu", ACTION=="remove", GOTO="kdump_reload"
-SUBSYSTEM=="memory", ACTION=="online", GOTO="kdump_reload"
-SUBSYSTEM=="memory", ACTION=="offline", GOTO="kdump_reload"
-
-GOTO="kdump_reload_end"
-
-LABEL="kdump_reload"
-
-# If kdump is not loaded, calling kdump-udev-throttle will end up
-# doing nothing, but systemd-run will always generate extra logs for
-# each call, so trigger the kdump-udev-throttler only if kdump
-# service is active to avoid unnecessary logs
-RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'"
-
-LABEL="kdump_reload_end"

SOURCES/98-kexec.rules.ppc64

@@ -1,22 +0,0 @@
-SUBSYSTEM=="cpu", ACTION=="online", GOTO="kdump_reload_cpu"
-SUBSYSTEM=="memory", ACTION=="online", GOTO="kdump_reload_mem"
-SUBSYSTEM=="memory", ACTION=="offline", GOTO="kdump_reload_mem"
-
-GOTO="kdump_reload_end"
-
-# If kdump is not loaded, calling kdump-udev-throttle will end up
-# doing nothing, but systemd-run will always generate extra logs for
-# each call, so trigger the kdump-udev-throttler only if kdump
-# service is active to avoid unnecessary logs
-
-LABEL="kdump_reload_mem"
-
-RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'"
-
-GOTO="kdump_reload_end"
-
-LABEL="kdump_reload_cpu"
-
-RUN+="/bin/sh -c '/usr/bin/systemctl is-active kdump.service || exit 0; ! test -f /sys/kernel/fadump_enabled || cat /sys/kernel/fadump_enabled | grep 0  || exit 0; /usr/bin/systemd-run --quiet --no-block /usr/lib/udev/kdump-udev-throttler'"
-
-LABEL="kdump_reload_end"

SOURCES/dracut-early-kdump-module-setup.sh

@@ -1,64 +0,0 @@
-#!/bin/bash
-
-. /etc/sysconfig/kdump
-
-KDUMP_KERNEL=""
-KDUMP_INITRD=""
-
-check() {
-    if [ ! -f /etc/sysconfig/kdump ] || [ ! -f /lib/kdump/kdump-lib.sh ]\
-        || [ -n "${IN_KDUMP}" ]
-    then
-        return 1
-    fi
-    return 255
-}
-
-depends() {
-    echo "base shutdown"
-    return 0
-}
-
-prepare_kernel_initrd() {
-    . /lib/kdump/kdump-lib.sh
-
-    prepare_kdump_bootinfo
-
-    # $kernel is a variable from dracut
-    if [ "$KDUMP_KERNELVER" != $kernel ]; then
-        dwarn "Using kernel version '$KDUMP_KERNELVER' for early kdump," \
-            "but the initramfs is generated for kernel version '$kernel'"
-    fi
-}
-
-install() {
-    prepare_kernel_initrd
-    if [ ! -f "$KDUMP_KERNEL" ]; then
-        derror "Could not find required kernel for earlykdump," \
-            "earlykdump will not work!"
-        return 1
-    fi
-    if [ ! -f "$KDUMP_INITRD" ]; then
-        derror "Could not find required kdump initramfs for earlykdump," \
-            "please ensure kdump initramfs is generated first," \
-            "earlykdump will not work!"
-        return 1
-    fi
-
-    inst_multiple tail find cut dirname hexdump
-    inst_simple "/etc/sysconfig/kdump"
-    inst_binary "/usr/sbin/kexec"
-    inst_binary "/usr/bin/gawk" "/usr/bin/awk"
-    inst_binary "/usr/bin/logger" "/usr/bin/logger"
-    inst_binary "/usr/bin/printf" "/usr/bin/printf"
-    inst_script "/lib/kdump/kdump-lib.sh" "/lib/kdump-lib.sh"
-    inst_script "/lib/kdump/kdump-logger.sh" "/lib/kdump-logger.sh"
-    inst_hook cmdline 00 "$moddir/early-kdump.sh"
-    inst_binary "$KDUMP_KERNEL"
-    inst_binary "$KDUMP_INITRD"
-
-    ln_r "$KDUMP_KERNEL" "/boot/kernel-earlykdump"
-    ln_r "$KDUMP_INITRD" "/boot/initramfs-earlykdump"
-
-    chmod -x "${initdir}/$KDUMP_KERNEL"
-}

SOURCES/dracut-early-kdump.sh

@@ -1,83 +0,0 @@
-#! /bin/sh
-
-KEXEC=/sbin/kexec
-standard_kexec_args="-p"
-
-EARLY_KDUMP_INITRD=""
-EARLY_KDUMP_KERNEL=""
-EARLY_KDUMP_CMDLINE=""
-EARLY_KDUMP_KERNELVER=""
-EARLY_KEXEC_ARGS=""
-
-. /etc/sysconfig/kdump
-. /lib/dracut-lib.sh
-. /lib/kdump-lib.sh
-. /lib/kdump-logger.sh
-
-#initiate the kdump logger
-dlog_init
-if [ $? -ne 0 ]; then
-        echo "failed to initiate the kdump logger."
-        exit 1
-fi
-
-prepare_parameters()
-{
-    EARLY_KDUMP_CMDLINE=$(prepare_cmdline "${KDUMP_COMMANDLINE}" "${KDUMP_COMMANDLINE_REMOVE}" "${KDUMP_COMMANDLINE_APPEND}")
-    EARLY_KDUMP_KERNEL="/boot/kernel-earlykdump"
-    EARLY_KDUMP_INITRD="/boot/initramfs-earlykdump"
-}
-
-early_kdump_load()
-{
-    check_kdump_feasibility
-    if [ $? -ne 0 ]; then
-        return 1
-    fi
-
-    if is_fadump_capable; then
-        dwarn "WARNING: early kdump doesn't support fadump."
-        return 1
-    fi
-
-    check_current_kdump_status
-    if [ $? == 0 ]; then
-        return 1
-    fi
-
-    prepare_parameters
-
-    EARLY_KEXEC_ARGS=$(prepare_kexec_args "${KEXEC_ARGS}")
-
-    # Here, only output the messages, but do not save these messages
-    # to a file because the target disk may not be mounted yet, the
-    # earlykdump is too early.
-    ddebug "earlykdump: $KEXEC ${EARLY_KEXEC_ARGS} $standard_kexec_args \
-	--command-line=$EARLY_KDUMP_CMDLINE --initrd=$EARLY_KDUMP_INITRD \
-	$EARLY_KDUMP_KERNEL"
-
-    $KEXEC ${EARLY_KEXEC_ARGS} $standard_kexec_args \
-        --command-line="$EARLY_KDUMP_CMDLINE" \
-        --initrd=$EARLY_KDUMP_INITRD $EARLY_KDUMP_KERNEL
-    if [ $? == 0 ]; then
-        dinfo "kexec: loaded early-kdump kernel"
-        return 0
-    else
-        derror "kexec: failed to load early-kdump kernel"
-        return 1
-    fi
-}
-
-set_early_kdump()
-{
-    if getargbool 0 rd.earlykdump; then
-        dinfo "early-kdump is enabled."
-        early_kdump_load
-    else
-        dinfo "early-kdump is disabled."
-    fi
-
-    return 0
-}
-
-set_early_kdump

SOURCES/dracut-fadump-init-fadump.sh

@@ -1,48 +0,0 @@
-#!/bin/sh
-export PATH=/usr/bin:/usr/sbin
-export SYSTEMD_IN_INITRD=lenient
-
-[ -e /proc/mounts ] ||
-	(mkdir -p /proc && mount -t proc -o nosuid,noexec,nodev proc /proc)
-
-grep -q '^sysfs /sys sysfs' /proc/mounts ||
-	(mkdir -p /sys && mount -t sysfs -o nosuid,noexec,nodev sysfs /sys)
-
-grep -q '^none / ' /proc/mounts || grep -q '^rootfs / ' /proc/mounts && ROOTFS_IS_RAMFS=1
-
-if [ -f /proc/device-tree/rtas/ibm,kernel-dump ] || [ -f /proc/device-tree/ibm,opal/dump/mpipl-boot ]; then
-	mkdir /newroot
-	mount -t ramfs ramfs /newroot
-
-	if [ $ROOTFS_IS_RAMFS ]; then
-		for FILE in $(ls -A /fadumproot/); do
-			mv /fadumproot/$FILE /newroot/
-		done
-		exec switch_root /newroot /init
-	else
-		mkdir /newroot/sys /newroot/proc /newroot/dev /newroot/run /newroot/oldroot
-
-		grep -q '^devtmpfs /dev devtmpfs' /proc/mounts && mount --move /dev /newroot/dev
-		grep -q '^tmpfs /run tmpfs' /proc/mounts && mount --move /run /newroot/run
-		mount --move /sys /newroot/sys
-		mount --move /proc /newroot/proc
-
-		cp --reflink=auto --sparse=auto --preserve=mode,timestamps,links -dfr /fadumproot/. /newroot/
-		cd /newroot && pivot_root . oldroot
-
-		loop=1
-		while [ $loop ]; do
-			unset loop
-			while read -r _ mp _; do
-				case $mp in
-				/oldroot/*) umount -d "$mp" && loop=1 ;;
-				esac
-			done </proc/mounts
-		done
-		umount -d -l oldroot
-
-		exec /init
-	fi
-else
-	exec /init.dracut
-fi

SOURCES/dracut-fadump-module-setup.sh

@@ -1,23 +0,0 @@
-#!/bin/bash
-
-check() {
-    return 255
-}
-
-depends() {
-    return 0
-}
-
-install() {
-    mv -f "$initdir/init" "$initdir/init.dracut"
-    inst_script "$moddir/init-fadump.sh" /init
-    chmod a+x "$initdir/init"
-
-    # Install required binaries for the init script (init-fadump.sh)
-    inst_multiple sh modprobe grep mkdir mount
-    if dracut_module_included "squash"; then
-        inst_multiple cp pivot_root umount
-    else
-        inst_multiple ls mv switch_root
-    fi
-}

SOURCES/dracut-kdump-capture.service

@@ -1,30 +0,0 @@
-#  This file is part of systemd.
-#
-#  systemd is free software; you can redistribute it and/or modify it
-#  under the terms of the GNU Lesser General Public License as published by
-#  the Free Software Foundation; either version 2.1 of the License, or
-#  (at your option) any later version.
-
-[Unit]
-Description=Kdump Vmcore Save Service
-After=initrd.target initrd-parse-etc.service sysroot.mount
-After=dracut-initqueue.service dracut-pre-mount.service dracut-mount.service dracut-pre-pivot.service
-Before=initrd-cleanup.service
-ConditionPathExists=/etc/initrd-release
-OnFailure=emergency.target
-OnFailureJobMode=isolate
-
-[Service]
-Environment=DRACUT_SYSTEMD=1
-Environment=NEWROOT=/sysroot
-Type=oneshot
-ExecStart=/bin/kdump.sh
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog+console
-KillMode=process
-RemainAfterExit=yes
-
-# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash
-# terminates cleanly.
-KillSignal=SIGHUP

SOURCES/dracut-kdump-emergency.service

@@ -1,28 +0,0 @@
-#  This file is part of systemd.
-#
-#  systemd is free software; you can redistribute it and/or modify it
-#  under the terms of the GNU Lesser General Public License as published by
-#  the Free Software Foundation; either version 2.1 of the License, or
-#  (at your option) any later version.
-
-# This service will be placed in kdump initramfs and replace both the systemd
-# emergency service and dracut emergency shell. IOW, any emergency will be
-# kick this service and in turn isolating to kdump error handler.
-
-[Unit]
-Description=Kdump Emergency
-DefaultDependencies=no
-IgnoreOnIsolate=yes
-
-[Service]
-ExecStart=/usr/bin/systemctl --no-block isolate kdump-error-handler.service
-Type=oneshot
-StandardInput=tty-force
-StandardOutput=inherit
-StandardError=inherit
-KillMode=process
-IgnoreSIGPIPE=no
-
-# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash
-# terminates cleanly.
-KillSignal=SIGHUP

SOURCES/dracut-kdump-emergency.target

@@ -1,14 +0,0 @@
-#  This file is part of systemd.
-#
-#  systemd is free software; you can redistribute it and/or modify it
-#  under the terms of the GNU Lesser General Public License as published by
-#  the Free Software Foundation; either version 2.1 of the License, or
-#  (at your option) any later version.
-
-[Unit]
-Description=Emergency Mode
-Documentation=man:systemd.special(7)
-Requires=emergency.service
-After=emergency.service
-AllowIsolate=yes
-IgnoreOnIsolate=yes

SOURCES/dracut-kdump-error-handler.service

@@ -1,33 +0,0 @@
-#  This file is part of systemd.
-#
-#  systemd is free software; you can redistribute it and/or modify it
-#  under the terms of the GNU Lesser General Public License as published by
-#  the Free Software Foundation; either version 2.1 of the License, or
-#  (at your option) any later version.
-
-# This service will run the real kdump error handler code. Executing the
-# failure action configured in kdump.conf
-
-[Unit]
-Description=Kdump Error Handler
-DefaultDependencies=no
-After=systemd-vconsole-setup.service
-Wants=systemd-vconsole-setup.service
-AllowIsolate=yes
-
-[Service]
-Environment=HOME=/
-Environment=DRACUT_SYSTEMD=1
-Environment=NEWROOT=/sysroot
-WorkingDirectory=/
-ExecStart=/bin/kdump-error-handler.sh
-Type=oneshot
-StandardInput=tty-force
-StandardOutput=inherit
-StandardError=inherit
-KillMode=process
-IgnoreSIGPIPE=no
-
-# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash
-# terminates cleanly.
-KillSignal=SIGHUP

SOURCES/dracut-kdump-error-handler.sh

@@ -1,10 +0,0 @@
-#!/bin/sh
-
-. /lib/kdump-lib-initramfs.sh
-
-set -o pipefail
-export PATH=$PATH:$KDUMP_SCRIPT_DIR
-
-get_kdump_confs
-do_failure_action
-do_final_action

SOURCES/dracut-kdump.sh

@@ -1,324 +0,0 @@
-#!/bin/sh
-
-# continue here only if we have to save dump.
-if [ -f /etc/fadump.initramfs ] && [ ! -f /proc/device-tree/rtas/ibm,kernel-dump ] && [ ! -f /proc/device-tree/ibm,opal/dump/mpipl-boot ]; then
-    exit 0
-fi
-
-. /lib/dracut-lib.sh
-. /lib/kdump-lib-initramfs.sh
-
-set -o pipefail
-DUMP_RETVAL=0
-
-export PATH=$PATH:$KDUMP_SCRIPT_DIR
-
-do_dump()
-{
-    local _ret
-
-    eval $DUMP_INSTRUCTION
-    _ret=$?
-
-    if [ $_ret -ne 0 ]; then
-        derror "saving vmcore failed"
-    fi
-
-    return $_ret
-}
-
-do_kdump_pre()
-{
-    local _ret
-
-    if [ -n "$KDUMP_PRE" ]; then
-        "$KDUMP_PRE"
-        _ret=$?
-        if [ $_ret -ne 0 ]; then
-            derror "$KDUMP_PRE exited with $_ret status"
-            return $_ret
-        fi
-    fi
-
-    # if any script fails, it just raises warning and continues
-    if [ -d /etc/kdump/pre.d ]; then
-        for file in /etc/kdump/pre.d/*; do
-            "$file"
-            _ret=$?
-            if [ $_ret -ne 0 ]; then
-                derror "$file exited with $_ret status"
-            fi
-        done
-    fi
-    return 0
-}
-
-do_kdump_post()
-{
-    local _ret
-
-    if [ -d /etc/kdump/post.d ]; then
-        for file in /etc/kdump/post.d/*; do
-            "$file" "$1"
-            _ret=$?
-            if [ $_ret -ne 0 ]; then
-                derror "$file exited with $_ret status"
-            fi
-        done
-    fi
-
-    if [ -n "$KDUMP_POST" ]; then
-        "$KDUMP_POST" "$1"
-        _ret=$?
-        if [ $_ret -ne 0 ]; then
-            derror "$KDUMP_POST exited with $_ret status"
-        fi
-    fi
-}
-
-add_dump_code()
-{
-    DUMP_INSTRUCTION=$1
-}
-
-dump_raw()
-{
-    local _raw=$1
-
-    [ -b "$_raw" ] || return 1
-
-    dinfo "saving to raw disk $_raw"
-
-    if ! $(echo -n $CORE_COLLECTOR|grep -q makedumpfile); then
-        _src_size=`ls -l /proc/vmcore | cut -d' ' -f5`
-        _src_size_mb=$(($_src_size / 1048576))
-        monitor_dd_progress $_src_size_mb &
-    fi
-
-    dinfo "saving vmcore"
-    $CORE_COLLECTOR /proc/vmcore | dd of=$_raw bs=$DD_BLKSIZE >> /tmp/dd_progress_file 2>&1 || return 1
-    sync
-
-    dinfo "saving vmcore complete"
-    return 0
-}
-
-dump_ssh()
-{
-    local _ret=0
-    local _exitcode=0 _exitcode2=0
-    local _opt="-i $1 -o BatchMode=yes -o StrictHostKeyChecking=yes"
-    local _dir="$KDUMP_PATH/$HOST_IP-$DATEDIR"
-    local _host=$2
-    local _vmcore="vmcore"
-    local _ipv6_addr="" _username=""
-
-    dinfo "saving to $_host:$_dir"
-
-    cat /var/lib/random-seed > /dev/urandom
-    ssh -q $_opt $_host mkdir -p $_dir || return 1
-
-    save_vmcore_dmesg_ssh ${DMESG_COLLECTOR} ${_dir} "${_opt}" $_host
-    save_opalcore_ssh ${_dir} "${_opt}" $_host
-
-    dinfo "saving vmcore"
-
-    if is_ipv6_address "$_host"; then
-        _username=${_host%@*}
-        _ipv6_addr="[${_host#*@}]"
-    fi
-
-    if [ "${CORE_COLLECTOR%%[[:blank:]]*}" = "scp" ]; then
-        if [ -n "$_username" ] && [ -n "$_ipv6_addr" ]; then
-            scp -q $_opt /proc/vmcore "$_username@$_ipv6_addr:$_dir/vmcore-incomplete"
-        else
-            scp -q $_opt /proc/vmcore "$_host:$_dir/vmcore-incomplete"
-        fi
-        _exitcode=$?
-    else
-        $CORE_COLLECTOR /proc/vmcore | ssh $_opt $_host "umask 0077 && dd bs=512 of=$_dir/vmcore-incomplete"
-        _exitcode=$?
-        _vmcore="vmcore.flat"
-    fi
-
-    if [ $_exitcode -eq 0 ]; then
-        ssh $_opt $_host "mv $_dir/vmcore-incomplete $_dir/$_vmcore"
-        _exitcode2=$?
-        if [ $_exitcode2 -ne 0 ]; then
-            derror "moving vmcore failed, _exitcode:$_exitcode2"
-        else
-            dinfo "saving vmcore complete"
-        fi
-    else
-        derror "saving vmcore failed, _exitcode:$_exitcode"
-    fi
-
-    dinfo "saving the $KDUMP_LOG_FILE to $_host:$_dir/"
-    save_log
-    if [ -n "$_username" ] && [ -n "$_ipv6_addr" ]; then
-        scp -q $_opt $KDUMP_LOG_FILE "$_username@$_ipv6_addr:$_dir/"
-    else
-        scp -q $_opt $KDUMP_LOG_FILE "$_host:$_dir/"
-    fi
-    _ret=$?
-    if [ $_ret -ne 0 ]; then
-        derror "saving log file failed, _exitcode:$_ret"
-    fi
-
-    if [ $_exitcode -ne 0 ] || [ $_exitcode2 -ne 0 ];then
-        return 1
-    fi
-
-    return 0
-}
-
-save_opalcore_ssh() {
-    local _path=$1
-    local _opts="$2"
-    local _location=$3
-    local _user_name="" _ipv6addr=""
-
-    ddebug "_path=$_path _opts=$_opts _location=$_location"
-
-    if [ ! -f $OPALCORE ]; then
-        # Check if we are on an old kernel that uses a different path
-        if [ -f /sys/firmware/opal/core ]; then
-            OPALCORE="/sys/firmware/opal/core"
-        else
-            return 0
-        fi
-    fi
-
-    if is_ipv6_address "$_host"; then
-        _user_name=${_location%@*}
-        _ipv6addr="[${_location#*@}]"
-    fi
-
-    dinfo "saving opalcore:$OPALCORE to $_location:$_path"
-
-    if [ -n "$_user_name" ] && [ -n "$_ipv6addr" ]; then
-        scp $_opts $OPALCORE $_user_name@$_ipv6addr:$_path/opalcore-incomplete
-    else
-        scp $_opts $OPALCORE $_location:$_path/opalcore-incomplete
-    fi
-    if [ $? -ne 0 ]; then
-        derror "saving opalcore failed"
-       return 1
-    fi
-
-    ssh $_opts $_location mv $_path/opalcore-incomplete $_path/opalcore
-    dinfo "saving opalcore complete"
-    return 0
-}
-
-save_vmcore_dmesg_ssh() {
-    local _dmesg_collector=$1
-    local _path=$2
-    local _opts="$3"
-    local _location=$4
-
-    dinfo "saving vmcore-dmesg.txt to $_location:$_path"
-    $_dmesg_collector /proc/vmcore | ssh $_opts $_location "umask 0077 && dd of=$_path/vmcore-dmesg-incomplete.txt"
-    _exitcode=$?
-
-    if [ $_exitcode -eq 0 ]; then
-        ssh -q $_opts $_location mv $_path/vmcore-dmesg-incomplete.txt $_path/vmcore-dmesg.txt
-        dinfo "saving vmcore-dmesg.txt complete"
-    else
-        derror "saving vmcore-dmesg.txt failed"
-    fi
-}
-
-get_host_ip()
-{
-    local _host
-    if is_nfs_dump_target || is_ssh_dump_target
-    then
-        kdumpnic=$(getarg kdumpnic=)
-        [ -z "$kdumpnic" ] && derror "failed to get kdumpnic!" && return 1
-        _host=`ip addr show dev $kdumpnic|grep '[ ]*inet'`
-        [ $? -ne 0 ] && derror "wrong kdumpnic: $kdumpnic" && return 1
-        _host=`echo $_host | head -n 1 | cut -d' ' -f2`
-        _host="${_host%%/*}"
-        [ -z "$_host" ] && derror "wrong kdumpnic: $kdumpnic" && return 1
-        HOST_IP=$_host
-    fi
-    return 0
-}
-
-read_kdump_conf()
-{
-    if [ ! -f "$KDUMP_CONF" ]; then
-        derror "$KDUMP_CONF not found"
-        return
-    fi
-
-    get_kdump_confs
-
-    # rescan for add code for dump target
-    while read config_opt config_val;
-    do
-        # remove inline comments after the end of a directive.
-        case "$config_opt" in
-        dracut_args)
-            config_val=$(get_dracut_args_target "$config_val")
-            if [ -n "$config_val" ]; then
-                config_val=$(get_mntpoint_from_target "$config_val")
-                add_dump_code "dump_fs $config_val"
-            fi
-            ;;
-        ext[234]|xfs|btrfs|minix|nfs)
-            config_val=$(get_mntpoint_from_target "$config_val")
-            add_dump_code "dump_fs $config_val"
-            ;;
-        raw)
-            add_dump_code "dump_raw $config_val"
-            ;;
-        ssh)
-            add_dump_code "dump_ssh $SSH_KEY_LOCATION $config_val"
-            ;;
-        esac
-    done <<< "$(read_strip_comments $KDUMP_CONF)"
-}
-
-fence_kdump_notify()
-{
-    if [ -n "$FENCE_KDUMP_NODES" ]; then
-        $FENCE_KDUMP_SEND $FENCE_KDUMP_ARGS $FENCE_KDUMP_NODES &
-    fi
-}
-
-read_kdump_conf
-fence_kdump_notify
-
-get_host_ip
-if [ $? -ne 0 ]; then
-    derror "get_host_ip exited with non-zero status!"
-    exit 1
-fi
-
-if [ -z "$DUMP_INSTRUCTION" ]; then
-    add_dump_code "dump_fs $NEWROOT"
-fi
-
-do_kdump_pre
-if [ $? -ne 0 ]; then
-    derror "kdump_pre script exited with non-zero status!"
-    do_final_action
-    # During systemd service to reboot the machine, stop this shell script running
-    exit 1
-fi
-make_trace_mem "kdump saving vmcore" '1:shortmem' '2+:mem' '3+:slab'
-do_dump
-DUMP_RETVAL=$?
-
-do_kdump_post $DUMP_RETVAL
-if [ $? -ne 0 ]; then
-    derror "kdump_post script exited with non-zero status!"
-fi
-
-if [ $DUMP_RETVAL -ne 0 ]; then
-    exit 1
-fi
-
-do_final_action

SOURCES/dracut-monitor_dd_progress

@@ -1,28 +0,0 @@
-#!/bin/sh
-
-SRC_FILE_MB=$1
-
-while true
-do
-    DD_PID=`pidof dd`
-    if [ -n "$DD_PID" ]; then
-        break
-    fi
-done
-
-while true
-do
-    sleep 5
-    if [ ! -d /proc/$DD_PID ]; then
-        break
-    fi
-
-    kill -s USR1 $DD_PID
-    CURRENT_SIZE=`tail -n 1 /tmp/dd_progress_file | sed "s/[^0-9].*//g"`
-    [ -n "$CURRENT_SIZE" ] && {
-        CURRENT_MB=$(($CURRENT_SIZE / 1048576))
-        echo -e "Copied $CURRENT_MB MB / $SRC_FILE_MB MB\r"
-    }
-done
-
-rm -f /tmp/dd_progress_file

SOURCES/early-kdump-howto.txt

@@ -1,95 +0,0 @@
-Early Kdump HOWTO
-
-Introduction
-------------
-
-Early kdump is a mechanism to make kdump operational earlier than normal kdump
-service.  The kdump service starts early enough for general crash cases, but
-there are some cases where it has no chance to make kdump operational in boot
-sequence, such as detecting devices and starting early services.  If you hit
-such a case, early kdump may allow you to get more information of it.
-
-Early kdump is implemented as a dracut module.  It adds a kernel (vmlinuz) and
-initramfs for kdump to your system's initramfs in order to load them as early
-as possible.  After that, if you provide "rd.earlykdump" in kernel command line,
-then in the initramfs, early kdump will load those files like the normal kdump
-service.  This is disabled by default.
-
-For the normal kdump service, it can check whether the early kdump has loaded
-the crash kernel and initramfs. It has no conflict with the early kdump.
-
-How to configure early kdump
-----------------------------
-
-We assume if you're reading this document, you should already have kexec-tools
-installed.
-
-You can rebuild the initramfs with earlykdump support with below steps:
-
-1. start kdump service to make sure kdump initramfs is created.
-
-    # systemctl start kdump
-
-    NOTE: If a crash occurs during boot process, early kdump captures a vmcore
-    and reboot the system by default, so the system might go into crash loop.
-    You can avoid such a crash loop by adding the following settings, which
-    power off the system after dump capturing, to kdump.conf in advance:
-
-        final_action poweroff
-        failure_action poweroff
-
-    For the failure_action, you can choose anything other than "reboot".
-
-2. rebuild system initramfs with earlykdump support.
-
-    # dracut --force --add earlykdump
-
-    NOTE: Recommend to backup the original system initramfs before performing
-    this step to put it back if something happens during boot-up.
-
-3. add rd.earlykdump in grub kernel command line.
-
-After making said changes, reboot your system to take effect. Of course, if you
-want to disable early kdump, you can simply remove "rd.earlykdump" from kernel
-boot parameters in grub, and reboot system like above.
-
-Once the boot is completed, you can check the status of the early kdump support
-on the command prompt:
-
-    # journalctl -b | grep early-kdump
-
-Then, you will see some useful logs, for example:
-
-- if early kdump is successful.
-
-Mar 09 09:57:56 localhost dracut-cmdline[190]: early-kdump is enabled.
-Mar 09 09:57:56 localhost dracut-cmdline[190]: kexec: loaded early-kdump kernel
-
-- if early kdump is disabled.
-
-Mar 09 10:02:47 localhost dracut-cmdline[189]: early-kdump is disabled.
-
-Notes
------
-
-- The size of early kdump initramfs will be large because it includes vmlinuz
-  and kdump initramfs.
-
-- Early kdump inherits the settings of normal kdump, so any changes that
-  caused normal kdump rebuilding also require rebuilding the system initramfs
-  to make sure that the changes take effect for early kdump. Therefore, after
-  the rebuilding of kdump initramfs is completed, provide a prompt message to
-  tell the fact.
-
-- If you install an updated kernel and reboot the system with it, the early
-  kdump will be disabled by default.  To enable it with the new kernel, you
-  need to take the above steps again.
-
-Limitation
-----------
-
-- At present, early kdump doesn't support fadump.
-
-- Early kdump loads a crash kernel and initramfs at the beginning of the
-  process in system's initramfs, so a crash at earlier than that (e.g. in
-  kernel initialization) cannot be captured even with the early kdump.

SOURCES/fadump-howto.txt

@@ -1,352 +0,0 @@
-Firmware assisted dump (fadump) HOWTO
-
-Introduction
-
-Firmware assisted dump is a new feature in the 3.4 mainline kernel supported
-only on powerpc architecture. The goal of firmware-assisted dump is to enable
-the dump of a crashed system, and to do so from a fully-reset system, and to
-minimize the total elapsed time until the system is back in production use. A
-complete documentation on implementation can be found at
-Documentation/powerpc/firmware-assisted-dump.txt in upstream linux kernel tree
-from 3.4 version and above.
-
-Please note that the firmware-assisted dump feature is only available on Power6
-and above systems with recent firmware versions.
-
-Overview
-
-Fadump
-
-Fadump is a robust kernel crash dumping mechanism to get reliable kernel crash
-dump with assistance from firmware. This approach does not use kexec, instead
-firmware assists in booting the kdump kernel while preserving memory contents.
-Unlike kdump, the system is fully reset, and loaded with a fresh copy of the
-kernel. In particular, PCI and I/O devices are reinitialized and are in a
-clean, consistent state.  This second kernel, often called a capture kernel,
-boots with very little memory and captures the dump image.
-
-The first kernel registers the sections of memory with the Power firmware for
-dump preservation during OS initialization. These registered sections of memory
-are reserved by the first kernel during early boot. When a system crashes, the
-Power firmware fully resets the system, preserves all the system memory
-contents, save the low memory (boot memory of size larger of 5% of system
-RAM or 256MB) of RAM to the previous registered region. It will also save
-system registers, and hardware PTE's.
-
-Fadump is supported only on ppc64 platform. The standard kernel and capture
-kernel are one and the same on ppc64.
-
-If you're reading this document, you should already have kexec-tools
-installed. If not, you install it via the following command:
-
-    # yum install kexec-tools
-
-Fadump Operational Flow:
-
-Like kdump, fadump also exports the ELF formatted kernel crash dump through
-/proc/vmcore. Hence existing kdump infrastructure can be used to capture fadump
-vmcore. The idea is to keep the functionality transparent to end user. From
-user perspective there is no change in the way kdump init script works.
-
-However, unlike kdump, fadump does not pre-load kdump kernel and initrd into
-reserved memory, instead it always uses default OS initrd during second boot
-after crash. Hence, for fadump, we rebuild the new kdump initrd and replace it
-with default initrd. Before replacing existing default initrd we take a backup
-of original default initrd for user's reference. The dracut package has been
-enhanced to rebuild the default initrd with vmcore capture steps. The initrd
-image is rebuilt as per the configuration in /etc/kdump.conf file.
-
-The control flow of fadump works as follows:
-01. System panics.
-02. At the crash, kernel informs power firmware that kernel has crashed.
-03. Firmware takes the control and reboots the entire system preserving
-    only the memory (resets all other devices).
-04. The reboot follows the normal booting process (non-kexec).
-05. The boot loader loads the default kernel and initrd from /boot
-06. The default initrd loads and runs /init
-07. dracut-kdump.sh script present in fadump aware default initrd checks if
-    '/proc/device-tree/rtas/ibm,kernel-dump'  file exists  before executing
-    steps to capture vmcore.
-    (This check will help to bypass the vmcore capture steps during normal boot
-     process.)
-09. Captures dump according to /etc/kdump.conf
-10. Is dump capture successful (yes goto 12, no goto 11)
-11. Perform the failure action specified in /etc/kdump.conf
-    (The default failure action is reboot, if unspecified)
-12. Perform the final action specified in /etc/kdump.conf
-    (The default final action is reboot, if unspecified)
-
-
-How to configure fadump:
-
-Again, we assume if you're reading this document, you should already have
-kexec-tools installed. If not, you install it via the following command:
-
-    # yum install kexec-tools
-
-Make the kernel to be configured with FADump as the default boot entry, if
-it isn't already:
-
-   # grubby --set-default=/boot/vmlinuz-<kver>
-
-Boot into the kernel to be configured for FADump. To be able to do much of
-anything interesting in the way of debug analysis, you'll also need to install
-the kernel-debuginfo package, of the same arch as your running kernel, and the
-crash utility:
-
-    # yum --enablerepo=\*debuginfo install kernel-debuginfo.$(uname -m) crash
-
-Next up, we need to modify some boot parameters to enable firmware assisted
-dump. With the help of grubby, it's very easy to append "fadump=on" to the end
-of your kernel boot parameters. To reserve the appropriate amount of memory
-for boot memory preservation, pass 'crashkernel=X' kernel cmdline parameter.
-For the recommended value of X, see 'FADump Memory Requirements' section.
-
-   # grubby --args="fadump=on crashkernel=6G" --update-kernel=/boot/vmlinuz-`uname -r`
-
-By default, FADump reserved memory will be initialized as CMA area to make the
-memory available through CMA allocator on the production kernel. We can opt out
-of this, making reserved memory unavailable to production kernel, by booting the
-linux kernel with 'fadump=nocma' instead of 'fadump=on'.
-
-The term 'boot memory' means size of the low memory chunk that is required for
-a kernel to boot successfully when booted with restricted memory.  By default,
-the boot memory size will be the larger of 5% of system RAM or 256MB.
-Alternatively, user can also specify boot memory size through boot parameter
-'fadump_reserve_mem=' which will override the default calculated size. Use this
-option if default boot memory size is not sufficient for second kernel to boot
-successfully.
-
-After making said changes, reboot your system, so that the specified memory is
-reserved and left untouched by the normal system. Take note that the output of
-'free -m' will show X MB less memory than without this parameter, which is
-expected. If you see OOM (Out Of Memory) error messages while loading capture
-kernel, then you should bump up the memory reservation size.
-
-Now that you've got that reserved memory region set up, you want to turn on
-the kdump init script:
-
-    # systemctl enable kdump.service
-
-Then, start up kdump as well:
-
-    # systemctl start kdump.service
-
-This should turn on the firmware assisted functionality in kernel by
-echo'ing 1 to /sys/kernel/fadump_registered, leaving the system ready
-to capture a vmcore upon crashing. For journaling filesystems like XFS an
-additional step is required to ensure bootloader does not pick the
-older initrd (without vmcore capture scripts):
-
-  * If /boot is a separate partition, run the below commands as the root user,
-    or as a user with CAP_SYS_ADMIN rights:
-
-        # fsfreeze -f
-        # fsfreeze -u
-
-  * If /boot is not a separate partition, reboot the system.
-
-After reboot check if the kdump service is up and running with:
-
-  # systemctl status kdump.service
-
-To test out whether FADump is configured properly, you can force-crash your
-system by echo'ing a 'c' into /proc/sysrq-trigger:
-
-    # echo c > /proc/sysrq-trigger
-
-You should see some panic output, followed by the system reset and booting into
-fresh copy of kernel. When default initrd loads and runs /init, vmcore should
-be copied out to disk (by default, in /var/crash/<YYYY.MM.DD-HH:MM:SS>/vmcore),
-then the system rebooted back into your normal kernel.
-
-Once back to your normal kernel, you can use the previously installed crash
-kernel in conjunction with the previously installed kernel-debuginfo to
-perform postmortem analysis:
-
-    # crash /usr/lib/debug/lib/modules/2.6.17-1.2621.el5/vmlinux
-    /var/crash/2006-08-23-15:34/vmcore
-
-    crash> bt
-
-and so on...
-
-Saving vmcore-dmesg.txt
------------------------
-Kernel log bufferes are one of the most important information available
-in vmcore. Now before saving vmcore, kernel log bufferes are extracted
-from /proc/vmcore and saved into a file vmcore-dmesg.txt. After
-vmcore-dmesg.txt, vmcore is saved. Destination disk and directory for
-vmcore-dmesg.txt is same as vmcore. Note that kernel log buffers will
-not be available if dump target is raw device.
-
-FADump Memory Requirements:
-
-  System Memory          Recommended memory
---------------------- ----------------------
-    4 GB - 16 GB     :        768 MB
-   16 GB - 64 GB     :       1024 MB
-   64 GB - 128 GB    :          2 GB
-  128 GB - 1 TB      :          4 GB
-    1 TB - 2 TB      :          6 GB
-    2 TB - 4 TB      :         12 GB
-    4 TB - 8 TB      :         20 GB
-    8 TB - 16 TB     :         36 GB
-   16 TB - 32 TB     :         64 GB
-   32 TB - 64 TB     :        128 GB
-   64 TB & above     :        180 GB
-
-Things to remember:
-
-1) The memory required to boot capture Kernel is a moving target that depends
-   on many factors like hardware attached to the system, kernel and modules in
-   use, packages installed and services enabled, there is no one-size-fits-all.
-   But the above recommendations are based on system memory. So, the above
-   recommendations for FADump come with a few assumptions, based on available
-   system memory, about the resources the system could have. So, please take
-   the recommendations with a pinch of salt and remember to try capturing dump
-   a few times to confirm that the system is configured successfully with dump
-   capturing support.
-
-2) Though the memory requirements for FADump seem high, this memory is not
-   completely set aside but made available for userspace applications to use,
-   through the CMA allocator.
-
-3) As the same initrd is used for booting production kernel as well as capture
-   kernel and with dump being captured in a restricted memory environment, few
-   optimizations (like not inclding network dracut module, disabling multipath
-   and such) are applied while building the initrd. In case, the production
-   environment needs these optimizations to be avoided, dracut_args option in
-   /etc/kdump.conf file could be leveraged. For example, if a user wishes for
-   network module to be included in the initrd, adding the below entry in
-   /etc/kdump.conf file and restarting kdump service would take care of it.
-
-   dracut_args --add "network"
-
-4) If FADump is configured to capture vmcore to a remote dump target using SSH
-   or NFS protocol, the corresponding network interface '<interface-name>' is
-   renamed to 'kdump-<interface-name>', if it is generic (like *eth# or net#).
-   It happens because vmcore capture scripts in the initial RAM disk (initrd)
-   add the 'kdump-' prefix to the network interface name to secure persistent
-   naming. And as capture kernel and production kernel use the same initrd in
-   case of FADump, the interface name is changed for the production kernel too.
-   This is likely to impact network configuration setup for production kernel.
-   So, it is recommended to use a non-generic name for a network interface,
-   before setting up FADump to capture vmcore to a remote dump target based on
-   that network interface, to avoid running into network configuration issues.
-
-Dump Triggering methods:
-
-This section talks about the various ways, other than a Kernel Panic, in which
-fadump can be triggered. The following methods assume that fadump is configured
-on your system, with the scripts enabled as described in the section above.
-
-1) AltSysRq C
-
-FAdump can be triggered with the combination of the 'Alt','SysRq' and 'C'
-keyboard keys. Please refer to the following link for more details:
-
-https://fedoraproject.org/wiki/QA/Sysrq
-
-In addition, on PowerPC boxes, fadump can also be triggered via Hardware
-Management Console(HMC) using 'Ctrl', 'O' and 'C' keyboard keys.
-
-2) Kernel OOPs
-
-If we want to generate a dump everytime the Kernel OOPses, we can achieve this
-by setting the 'Panic On OOPs' option as follows:
-
-    # echo 1 > /proc/sys/kernel/panic_on_oops
-
-3) PowerPC specific methods:
-
-On IBM PowerPC machines, issuing a soft reset invokes the XMON debugger(if
-XMON is configured). To configure XMON one needs to compile the kernel with
-the CONFIG_XMON and CONFIG_XMON_DEFAULT options, or by compiling with
-CONFIG_XMON and booting the kernel with xmon=on option.
-
-Following are the ways to remotely issue a soft reset on PowerPC boxes, which
-would drop you to XMON. Pressing a 'X' (capital alphabet X) followed by an
-'Enter' here will trigger the dump.
-
-3.1) HMC
-
-Hardware Management Console(HMC) available on Power4 and Power5 machines allow
-partitions to be reset remotely. This is specially useful in hang situations
-where the system is not accepting any keyboard inputs.
-
-Once you have HMC configured, the following steps will enable you to trigger
-fadump via a soft reset:
-
-On Power4
-  Using GUI
-
-    * In the right pane, right click on the partition you wish to dump.
-    * Select "Operating System->Reset".
-    * Select "Soft Reset".
-    * Select "Yes".
-
-  Using HMC Commandline
-
-    # reset_partition -m <machine> -p <partition> -t soft
-
-On Power5
-  Using GUI
-
-    * In the right pane, right click on the partition you wish to dump.
-    * Select "Restart Partition".
-    * Select "Dump".
-    * Select "OK".
-
-  Using HMC Commandline
-
-    # chsysstate -m <managed system name> -n <lpar name> -o dumprestart -r lpar
-
-3.2) Blade Management Console for Blade Center
-
-To initiate a dump operation, go to Power/Restart option under "Blade Tasks" in
-the Blade Management Console. Select the corresponding blade for which you want
-to initate the dump and then click "Restart blade with NMI". This issues a
-system reset and invokes xmon debugger.
-
-
-Advanced Setups & Failure action:
-
-Kdump and fadump exhibit similar behavior in terms of setup & failure action.
-For fadump advanced setup related information see section "Advanced Setups" in
-"kexec-kdump-howto.txt" document. Refer to "Failure action" section in "kexec-
-kdump-howto.txt" document for fadump failure action related information.
-
-Compression and filtering
-
-Refer "Compression and filtering" section in "kexec-kdump-howto.txt" document.
-Compression and filtering are same for kdump & fadump.
-
-
-Notes on rootfs mount:
-Dracut is designed to mount rootfs by default. If rootfs mounting fails it
-will refuse to go on. So fadump leaves rootfs mounting to dracut currently.
-We make the assumtion that proper root= cmdline is being passed to dracut
-initramfs for the time being. If you need modify "KDUMP_COMMANDLINE=" in
-/etc/sysconfig/kdump, you will need to make sure that appropriate root=
-options are copied from /proc/cmdline. In general it is best to append
-command line options using "KDUMP_COMMANDLINE_APPEND=" instead of replacing
-the original command line completely.
-
-How to disable FADump:
-
-Remove "fadump=on"/"fadump=nocma" from kernel cmdline parameters OR replace
-it with "fadump=off" kernel cmdline parameter:
-
-   # grubby --update-kernel=/boot/vmlinuz-`uname -r` --remove-args="fadump=on"
-or
-   # grubby --update-kernel=/boot/vmlinuz-`uname -r` --remove-args="fadump=nocma"
-OR
-   # grubby --update-kernel=/boot/vmlinuz-`uname -r` --args="fadump=off"
-
-If KDump is to be used as the dump capturing mechanism, update the crashkernel
-parameter (Else, remove "crashkernel=" parameter too, using grubby):
-
-   # grubby --update-kernel=/boot/vmlinuz-$kver --args="crashkernl=auto"
-
-Reboot the system for the settings to take effect.

SOURCES/gen-kdump-conf.sh

@@ -1,223 +0,0 @@
-#!/bin/bash
-# $1: target arch
-
-
-SED_EXP=""
-
-generate()
-{
-	sed "$SED_EXP" << EOF
-# This file contains a series of commands to perform (in order) in the kdump
-# kernel after a kernel crash in the crash kernel(1st kernel) has happened.
-#
-# Directives in this file are only applicable to the kdump initramfs, and have
-# no effect once the root filesystem is mounted and the normal init scripts are
-# processed.
-#
-# Currently, only one dump target and path can be specified.  If the dumping to
-# the configured target fails, the failure action which can be configured via
-# the "failure_action" directive will be performed.
-#
-# Supported options:
-#
-# raw <partition>
-#           - Will dd /proc/vmcore into <partition>.
-#             Use persistent device names for partition devices,
-#             such as /dev/vg/<devname>.
-#
-# nfs <nfs mount>
-#           - Will mount nfs to <mnt>, and copy /proc/vmcore to
-#             <mnt>/<path>/%HOST-%DATE/, supports DNS.
-#
-# ssh <user@server>
-#           - Will save /proc/vmcore to <user@server>:<path>/%HOST-%DATE/,
-#             supports DNS.
-#             NOTE: make sure the user has write permissions on the server.
-#
-# sshkey <path>
-#           - Will use the sshkey to do ssh dump.
-#             Specify the path of the ssh key to use when dumping
-#             via ssh. The default value is /root/.ssh/kdump_id_rsa.
-#
-# <fs type> <partition>
-#           - Will mount -t <fs type> <partition> <mnt>, and copy
-#             /proc/vmcore to <mnt>/<path>/%DATE/.
-#             NOTE: <partition> can be a device node, label or uuid.
-#             It's recommended to use persistent device names
-#             such as /dev/vg/<devname>.
-#             Otherwise it's suggested to use label or uuid.
-#
-# path <path>
-#           - "path" represents the file system path in which vmcore
-#             will be saved.  If a dump target is specified in
-#             kdump.conf, then "path" is relative to the specified
-#             dump target.
-#
-#             Interpretation of "path" changes a bit if the user didn't
-#             specify any dump target explicitly in kdump.conf.  In this
-#             case, "path" represents the absolute path from root. The
-#             dump target and adjusted path are arrived at automatically
-#             depending on what's mounted in the current system.
-#
-#             Ignored for raw device dumps.  If unset, will use the default
-#             "/var/crash".
-#
-# core_collector <command> <options>
-#           - This allows you to specify the command to copy
-#             the vmcore.  The default is makedumpfile, which on
-#             some architectures can drastically reduce vmcore size.
-#             See /sbin/makedumpfile --help for a list of options.
-#             Note that the -i and -g options are not needed here,
-#             as the initrd will automatically be populated with a
-#             config file appropriate for the running kernel.
-#             The default core_collector for raw/ssh dump is:
-#             "makedumpfile -F -l --message-level 7 -d 31".
-#             The default core_collector for other targets is:
-#             "makedumpfile -l --message-level 7 -d 31".
-#
-#             "makedumpfile -F" will create a flattened vmcore.
-#             You need to use "makedumpfile -R" to rearrange the dump data to
-#             a normal dumpfile readable with analysis tools.  For example:
-#             "makedumpfile -R vmcore < vmcore.flat".
-#
-#             For core_collector format details, you can refer to
-#             kexec-kdump-howto.txt or kdump.conf manpage.
-#
-# kdump_post <binary | script>
-#           - This directive allows you to run a executable binary
-#             or script after the vmcore dump process terminates.
-#             The exit status of the current dump process is fed to
-#             the executable binary or script as its first argument.
-#             All files under /etc/kdump/post.d are collectively sorted
-#             and executed in lexical order, before binary or script
-#             specified kdump_post parameter is executed.
-#
-# kdump_pre <binary | script>
-#           - Works like the "kdump_post" directive, but instead of running
-#             after the dump process, runs immediately before it.
-#             Exit status of this binary is interpreted as follows:
-#               0 - continue with dump process as usual
-#               non 0 - run the final action (reboot/poweroff/halt)
-#             All files under /etc/kdump/pre.d are collectively sorted and
-#             executed in lexical order, after binary or script specified
-#             kdump_pre parameter is executed.
-#             Even if the binary or script in /etc/kdump/pre.d directory
-#             returns non 0 exit status, the processing is continued.
-#
-# extra_bins <binaries | shell scripts>
-#           - This directive allows you to specify additional binaries or
-#             shell scripts to be included in the kdump initrd.
-#             Generally they are useful in conjunction with a kdump_post
-#             or kdump_pre binary or script which depends on these extra_bins.
-#
-# extra_modules <module(s)>
-#           - This directive allows you to specify extra kernel modules
-#             that you want to be loaded in the kdump initrd.
-#             Multiple modules can be listed, separated by spaces, and any
-#             dependent modules will automatically be included.
-#
-# failure_action <reboot | halt | poweroff | shell | dump_to_rootfs>
-#           - Action to perform in case dumping fails.
-#             reboot:   Reboot the system.
-#             halt:     Halt the system.
-#             poweroff: Power down the system.
-#             shell:    Drop to a bash shell.
-#                       Exiting the shell reboots the system by default,
-#                       or perform "final_action".
-#             dump_to_rootfs:  Dump vmcore to rootfs from initramfs context and
-#                       reboot by default or perform "final_action".
-#                       Useful when non-root dump target is specified.
-#             The default option is "reboot".
-#
-# default <reboot | halt | poweroff | shell | dump_to_rootfs>
-#           - Same as the "failure_action" directive above, but this directive
-#             is obsolete and will be removed in the future.
-#
-# final_action <reboot | halt | poweroff>
-#           - Action to perform in case dumping succeeds. Also performed
-#             when "shell" or "dump_to_rootfs" failure action finishes.
-#             Each action is same as the "failure_action" directive above.
-#             The default is "reboot".
-#
-# force_rebuild <0 | 1>
-#           - By default, kdump initrd will only be rebuilt when necessary.
-#             Specify 1 to force rebuilding kdump initrd every time when kdump
-#             service starts.
-#
-# force_no_rebuild <0 | 1>
-#           - By default, kdump initrd will be rebuilt when necessary.
-#             Specify 1 to bypass rebuilding of kdump initrd.
-#
-#             force_no_rebuild and force_rebuild options are mutually
-#             exclusive and they should not be set to 1 simultaneously.
-#
-# override_resettable <0 | 1>
-#           - Usually an unresettable block device can't be a dump target.
-#             Specifying 1 when you want to dump even though the block
-#             target is unresettable
-#             By default, it is 0, which will not try dumping destined to fail.
-#
-# dracut_args <arg(s)>
-#           - Pass extra dracut options when rebuilding kdump initrd.
-#
-# fence_kdump_args <arg(s)>
-#           - Command line arguments for fence_kdump_send (it can contain
-#             all valid arguments except hosts to send notification to).
-#
-# fence_kdump_nodes <node(s)>
-#           - List of cluster node(s) except localhost, separated by spaces,
-#             to send fence_kdump notifications to.
-#             (this option is mandatory to enable fence_kdump).
-#
-
-#raw /dev/vg/lv_kdump
-#ext4 /dev/vg/lv_kdump
-#ext4 LABEL=/boot
-#ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
-#nfs my.server.com:/export/tmp
-#nfs [2001:db8::1:2:3:4]:/export/tmp
-#ssh user@my.server.com
-#ssh user@2001:db8::1:2:3:4
-#sshkey /root/.ssh/kdump_id_rsa
-path /var/crash
-core_collector makedumpfile -l --message-level 7 -d 31
-#core_collector scp
-#kdump_post /var/crash/scripts/kdump-post.sh
-#kdump_pre /var/crash/scripts/kdump-pre.sh
-#extra_bins /usr/bin/lftp
-#extra_modules gfs2
-#failure_action shell
-#force_rebuild 1
-#force_no_rebuild 1
-#dracut_args --omit-drivers "cfg80211 snd" --add-drivers "ext2 ext3"
-#fence_kdump_args -p 7410 -f auto -c 0 -i 10
-#fence_kdump_nodes node1 node2
-EOF
-}
-
-update_param()
-{
-	SED_EXP="${SED_EXP}s/^$1.*$/$1 $2/;"
-}
-
-case "$1" in
-aarch64)
-	;;
-i386)
-	;;
-ppc64)
-	;;
-ppc64le)
-	;;
-s390x)
-	update_param core_collector \
-		"makedumpfile -c --message-level 7 -d 31"
-	;;
-x86_64)
-	;;
-*)
-	echo "Warning: Unknown architecture '$1', using default kdump.conf template."
-	;;
-esac
-
-generate

SOURCES/kdump-dep-generator.sh

@@ -1,23 +0,0 @@
-#!/bin/sh
-