Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I've followed the directions here for my 12.04.2 Ubuntu Server running in VMware Fusion 5, and everything looks good, so I do a echo c > /proc/sysrq-trigger as root. It panics the kernel as expected, and then hangs after printing out a bunch of stack traces. I waited a few minutes to make sure any writes to disk (for the crash dump) finished, and I restarted the VM. When I log in again, ls /var/crash shows no files! Any idea how to get it to work, or whether it works at all?

share|improve this question

1 Answer 1

The reason why this doesn't work properly has been well documented for over three or so years now: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe#Release_specific_notes : On systems with <= 2G RAM we won't reserve enough memory for the crash kernel's initrd to fit. That will cause the crash-kernel to panic. See also these bug reports for reference and for the workaround detailed below: #785394 and #1235616

To fix this issue set

GRUB_CMDLINE_LINUX="crashkernel=128M"

in /etc/default/grub. n.b.: You cannot put this option into GRUB_CMDLINE_DEFAULT, because the the setting in /etc/grub.d/10_linux takes precedence over that.

To "permanently" fix the issue, edit `/etc/grub.d/10_linux and change the line

    GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M"

to

    GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA crashkernel=128M"
share|improve this answer
    
While this doesn't answer the question, I'll let it go because it satisfies the "partial answer" rule. –  jokerdino Oct 4 '13 at 16:07

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.