From Fedora Project Wiki

Line 16: Line 16:
 
# When rebooting after kernel panic ABRT should detect the new vmcore appearing in {{filename|/var/crash}}, create a crash report and notify
 
# When rebooting after kernel panic ABRT should detect the new vmcore appearing in {{filename|/var/crash}}, create a crash report and notify
 
you via the notification area
 
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.
 
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 09:58, 26 April 2012

Description

This test case tests the functionality of the ABRT vmcore feature.


How to test

Error creating thumbnail: File missing
Please note that this test probably can't be done using live cd.
  1. Ensure you have the plugin installed with the following command:
    • su -c 'yum install abrt-addon-vmcore'
  2. Ensure you have necessary packages for producing vmcore and its processing:
    • su -c 'yum install kexec-tools crash system-config-kdump'
  3. 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'
Error creating thumbnail: File missing
System-config-kdump is broken in Fedora 17 - edit /etc/default/grub instead, then run grub2-mkconfig > /etc/grub2.cfg
  1. Add "crashkernel=128M" to kernel command line (say, via system-config-kdump -> "Enable", "Apply").
  2. Reboot.
  3. Ensure that the kdump service is running - systemctl status kdump.service. If it doesn't, no vmcore will be saved on crash.
  4. Crash the machine: sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger
  5. 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

Expected Results

  1. Step #1 completes without error
  2. The system boots into runlevel 5
  3. Program completes with exit code 0