On 01/08/2013 08:04 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 8:09 PM, Jim <binarynut@xxxxxxxxxxx> wrote:
On 01/07/2013 08:26 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 7:19 PM, Jim <binarynut@xxxxxxxxxxx> wrote:
On 01/07/2013 07:55 PM, Roger Heflin wrote:
correct grub line for
that kernel?
what correct grub line for that kernel ? it is in /boot/grub2/grub.conf
The line that booted the current kernel did not have a crashkernel
option on it, you either
have it on the wrong line in the grub.conf file, or a different
grub.conf is being used than you expect or it has
not been rebooted since the option was added.
Double check that link that was posted and make sure all is done right.
Thanks Roger, After I sent the reply it occurred to me what you were talking
about.
$cat /proc/cmdline
OOT_IMAGE=/boot/vmlinuz-3.5.2-1.fc17.i686
root=UUID=cf5a1042-bb2b-4c6b-a0e0-1da27273d413 ro rd.md=0 rd.lvm=0 rd.dm=0
SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
crashkernel=128M
I ran # systemctl start kdump.service and it still failed to start
I did restart the computer.
Error in messages for starting kdump;
Jan 7 21:07:12 localhost kdump: kexec: failed to load kdump kernel
Jan 7 21:07:12 localhost kdumpctl[1735]: Starting kdump:
Jan 7 21:07:12 localhost kdump: failed to start up
Jan 7 21:07:12 localhost systemd[1]: kdump.service: main process exited,
code=exited, status=1
Jan 7 21:07:12 localhost systemd[1]: Unit kdump.service entered failed
state.
/var/log/messages may tell you why it is erroring.
Note that kdump will rebuild the initird so if there is something
wrong with the initrd build process that will cause a failure.
Above is the only info I get from /var/log/messages .
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
