|
I I think grub isn't seeing my updated changes when I'm setting up
kdump on F-20. First I installed the the packages kexec-tools, crash, and kernel-debuginfo. Next I added crashkernel=128M to GRUB_CMDLINE_LINUX the in /etc/default/grub. Then I rebuild the grub config with: grub2-mkconfig -o /boot/grub2/grub.cfg and it creates the file ok. But, after rebooting, kdump hasn't started and I get the error from systemctl status kdump: kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: failed (Result: exit-code) since Mon 2014-05-26 19:15:03 EDT; 16min ago Process: 1308 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE) Main PID: 1308 (code=exited, status=1/FAILURE) CGroup: /system.slice/kdump.service May 26 19:15:03 tesla kdumpctl[1308]: No memory reserved for crash kernel. May 26 19:15:03 tesla kdumpctl[1308]: Starting kdump: [FAILED] May 26 19:15:03 tesla systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE May 26 19:15:03 tesla systemd[1]: Failed to start Crash recovery kernel arming. May 26 19:15:03 tesla systemd[1]: Unit kdump.service entered failed state. Which leads me to think that my grub.conf really isn't working for some reason. This is on an AMD system with 16 Gigs of ram, so available memory is definitely not a problem. Could be something else, but in any case I'm sure I'm missing something stupid ... Thanks. - Derrik |
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
