From Fedora Project Wiki
Description
This test case tests the functionality of the ABRT vmcore feature.
How to test
Please note that this test probably can't be done using live cd.
- Ensure you have the plugin installed with the following command:
su -c 'yum install abrt-addon-vmcore'
- Ensure you have necessary packages for producing vmcore and its processing:
su -c 'yum install kexec-tools crash system-config-kdump'
- Ensure that the system log watcher service is running -
systemctl status abrt-vmcore.service- If you have to change anything, restart abrtd:
su -c 'systemctl restart abrtd.service'
- If you have to change anything, restart abrtd:
System-config-kdump is broken in Fedora 17 - edit /etc/default/grub instead
- Add "crashkernel=128M" to kernel command line (say, via system-config-kdump -> "Enable", "Apply"). Reboot.
- Ensure that the kdump service is running -
systemctl status kdump.service. If it doesn't, no vmcore will be saved on crash. - Crash the machine:
sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger - When rebooting after kernel panic ABRT should detect the new vmcore appearing in
/var/crash, create a crash report and notify
you via the notification area
- Results of testing on F15: kexec worked, but apparently it tried to boot full-fledged F15 (instead of minimal kernel which saves vmcore). This failed since 128m is too small for that. Had to power-cycle the machine.
Expected Results
- Step #1 completes without error
- The system boots into runlevel 5
- Program completes with exit code 0