From Fedora Project Wiki
No edit summary |
No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
{{admon/note|Please note that this test probably can't be done using live cd.}} | {{admon/note|Please note that this test probably can't be done using live cd.}} | ||
# Ensure you have the plugin installed with the following command: | # Ensure you have the plugin installed with the following command: | ||
#* {{command|su -c ' | #* {{command|su -c 'dnf install abrt-addon-vmcore'}} | ||
# Ensure you have necessary packages for producing vmcore and its processing: | # Ensure you have necessary packages for producing vmcore and its processing: | ||
#* {{command|su -c ' | #* {{command|su -c 'dnf install kexec-tools system-config-kdump'}} | ||
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-vmcore.service}} | # Ensure that the system log watcher service is running - {{command|systemctl status abrt-vmcore.service}} | ||
#* If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}} | #* If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}} | ||
# Add | # Add <code>crashkernel=128M</code> to kernel command line. | ||
#* You can either use system-config-kdump, click "Enable" and then "Apply". | |||
#* Or you can manually edit {{filename|/etc/default/grub}} and then re-generate grub configuration file. | |||
# Reboot. | |||
# Ensure that the kdump service is running - {{command|systemctl status kdump.service}}. If it doesn't, no vmcore will be saved on crash. | # Ensure that the kdump service is running - {{command|systemctl status kdump.service}}. If it doesn't, no vmcore will be saved on crash. | ||
# Crash the machine: {{command|sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger}} | # Crash the machine: {{command|sync; echo 1 >/proc/sys/kernel/sysrq; echo c >/proc/sysrq-trigger}} | ||
# When rebooting after | |results= | ||
you via the notification area | # When rebooting after the crash, ABRT should detect the new vmcore appearing in {{filename|/var/crash}}, create a crash report and notify you via the notification area. | ||
}} | }} | ||
[[Category:Package_abrt_test_cases]] | [[Category:Package_abrt_test_cases]] | ||
Latest revision as of 11:54, 10 April 2015
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 'dnf install abrt-addon-vmcore'
- Ensure you have necessary packages for producing vmcore and its processing:
su -c 'dnf install kexec-tools 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:
- Add
crashkernel=128Mto kernel command line.- You can either use system-config-kdump, click "Enable" and then "Apply".
- Or you can manually edit
/etc/default/gruband then re-generate grub configuration file.
- 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
Expected Results
- When rebooting after the crash, ABRT should detect the new vmcore appearing in
/var/crash, create a crash report and notify you via the notification area.