From Fedora Project Wiki

No edit summary
 
(One intermediate revision by the same user not shown)
Line 6: Line 6:
#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:
{{admon/note|Find kdump-script here|http://hongqing.fedorapeople.org/script/kdump-script}}
     <pre>    ext4 /dev/mapper/vg_dhcp6558-lv_root  
     <pre>    ext4 /dev/mapper/vg_dhcp6558-lv_root  
     kdump_pre /bin/kdump-script
     kdump_pre /bin/kdump-script

Latest revision as of 02:55, 23 March 2012

Description

Setup

  1. Install Fedora 17 on your machine
  2. After system installed, check if kexec-tools 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_pre /bin/kdump-script
    extra_bins /usr/bin/crash
    extra_modules twofish
  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_Preextra_Bins_Modules&oldid=279568"