From Fedora Project Wiki

No edit summary
No edit summary
Line 9: Line 9:
     core_collector makedumpfile --nosuchoptions
     core_collector makedumpfile --nosuchoptions
     default halt </pre>
     default halt </pre>
#Apply changes and start kdump via service kdump restart
#Apply changes and start kdump via <pre>service kdump restart</pre>
|actions=
|actions=
#Trigger crash via: <pre>echo c > /proc/sysrq-trigger</pre>
#Trigger crash via: <pre>echo c > /proc/sysrq-trigger</pre>
|results=
|results=
#Test failed if <pre>cat /proc/cmdline | grep "crashkernel"</pre> got nothing means reserve crashkernel memory failed
#System halt
#Test failed if restart kdump failed
#Test suspend if rpm packages couldn't be installed
}}
}}
[[Category:Kdump_Test_Cases]]
[[Category:Kdump_Test_Cases]]

Revision as of 07:55, 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
  1. 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
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Kdump_Func_Halt&oldid=279342"