From Fedora Project Wiki

No edit summary
No edit summary
 
Line 5: Line 5:
#After system installed, check if kexec-tools kernel-debuginfo and crash is installed via <pre>rpm -q kexec-tools</pre> Or via yum <pre>yum install kexec-tools</pre>
#After system installed, check if kexec-tools kernel-debuginfo and crash is installed via <pre>rpm -q kexec-tools</pre> Or via yum <pre>yum install kexec-tools</pre>
#Reserve crashkernel for kdump by grubby <pre>grubby --args="crashkernl=128M" --update-kernel=$(grubby --default-kernel)</pre> Reboot system and check /proc/cmdline <pre>cat /proc/cmdline | grep "crashkernel"</pre>
#Reserve crashkernel for kdump by grubby <pre>grubby --args="crashkernl=128M" --update-kernel=$(grubby --default-kernel)</pre> Reboot system and check /proc/cmdline <pre>cat /proc/cmdline | grep "crashkernel"</pre>
#Edit /etc/kdump.conf. This is an example:
#Edit /etc/kdump.conf. This is an example:<pre> ext4 /dev/mapper/vg_dhcp6558-lv_root</pre><pre>core_collector makedumpfile --nosuchoptions</pre><pre>default halt </pre>
    :<pre>   ext4 /dev/mapper/vg_dhcp6558-lv_root
    core_collector makedumpfile --nosuchoptions
    default halt </pre>
#Apply changes and start kdump via <pre>service kdump restart</pre>
#Apply changes and start kdump via <pre>service kdump restart</pre>
|actions=
|actions=

Latest revision as of 08:19, 22 March 2012

Description

Setup

  1. Install Fedora 17 on your machine
  2. After system installed, check if kexec-tools kernel-debuginfo and crash is installed via
    rpm -q kexec-tools
    Or via yum
    yum install kexec-tools
  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. This is an example:
     ext4 /dev/mapper/vg_dhcp6558-lv_root
    core_collector makedumpfile --nosuchoptions
    default halt 
  5. Apply changes and start kdump via
    service kdump restart

How to test

  1. Trigger crash via:
    echo c > /proc/sysrq-trigger

Expected Results

  1. System halt