QA:Testcase Kdump Func DebugMem

From FedoraProject

Jump to: navigation, search

Contents

Description

Setup

  1. Install Fedora on your machine
  2. After system installed, check if kexec-tools kernel-debuginfo and crash is installed via
    rpm -q kexec-tools kernel-debuginfo crash
    If not, you can install via yum
    yum install kexec-tools kernel-debuginfo crash
  3. Reserve crashkernel for kdump by grubby
    grubby --args="crashkernl=128M" --update-kernel=$(grubby --default-kernel)
    Reboot system and check /proc/cmdline
    cat /proc/cmdline | grep "crashkernel"
  4. Edit /etc/kdump.conf, add this line:
     ext4 /dev/mapper/vg_dhcp6558-lv_root
     core_collector makedumpfile -E -d 31
  5. Apply changes and start kdump via
    service kdump restart
  6. Edit /etc/kdump.conf, add this line:
    debug_mem_level 0
    We should test 0/1/2/3.

How to test

  1. Trigger crash via:
    echo c > /proc/sysrq-trigger
  2. Check console output that debug_mem_level is enabled

Expected Results

  1. Dump process could be monitered if console is connected
  2. System reboot successfully after dump vmcore finshed
  3. More mem infos should be find via console