From Fedora Project Wiki

(Created page with "{{QA/Test_Case |description= |setup= #Install Fedora 17 on your machine #After system installed, check if kexec-tools kernel-debuginfo and crash is installed via <pre>rpm -q kexe...")
 
No edit summary
Line 14: Line 14:
#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
#From console could see Script excuted
#Test failed if restart kdump failed
#System reboot after process finished
#Test suspend if rpm packages couldn't be installed
 
}}
}}
[[Category:Kdump_Test_Cases]]
[[Category:Kdump_Test_Cases]]

Revision as of 07:57, 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 
    kdump_post /bin/kdump-script
    extra_bins /usr/bin/crash
    extra_modules twofish-x86_64
  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. From console could see Script excuted
  2. System reboot after process finished
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Kdump_Func_Postextra_Bins_Modules&oldid=279343"