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 is installed via <pre>rpm -q kexec-tools</pre> Or via yum <p...") |
No edit summary |
||
| Line 7: | Line 7: | ||
#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> ext4 /dev/mapper/vg_dhcp6558-lv_root | ||
kdump_pre /bin/kdump-script | |||
extra_bins /usr/bin/crash | extra_bins /usr/bin/crash | ||
extra_modules twofish</pre> | extra_modules twofish</pre> | ||
Revision as of 09:31, 22 March 2012
Description
Setup
- Install Fedora 17 on your machine
- After system installed, check if kexec-tools is installed via
rpm -q kexec-tools
Or via yumyum install kexec-tools
- Reserve crashkernel for kdump by grubby
grubby --args="crashkernl=128M" --update-kernel=$(grubby --default-kernel)
Reboot system and check /proc/cmdlinecat /proc/cmdline | grep "crashkernel"
- 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
- Apply changes and start kdump via service kdump restart
How to test
- Trigger crash via:
echo c > /proc/sysrq-trigger
Expected Results
- From console could see Script excuted
- System reboot after process finished