*** This bug is a duplicate of bug 785394 ***
https://bugs.launchpad.net/bugs/785394
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kexec-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 785394 ***
https://bugs.launchpad.net/bugs/785394
** This bug has been marked a duplicate of bug 785394
Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is
insufficient
--
You received this bug notification because you are a member
s/Debian/Ubuntu/ — I haven't actually tested this on Debian! (I don't
have any debian systems.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235616
Title:
linux-crashdump doesn't actually dump
Btw, just for completenes I have tested this on Debian now too, there
the crash kernel crashes. http://i.imgur.com/amCrAZW.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235616
Title:
Just about the same here on a few generic Ubuntu 12.04.2 VMs (using
KVM). Followed the documentation on
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe and
https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html which
basically says: install linux-crashdump, reboot, check /proc/cmdline,
make
Very interestingly, when setting `crashkernel=128M` instead of the
default `crashkernel=384M-2G:64M,2G-:128M`, crashing the machine works
correctly and also leaves a crashdump in /var/crash. Unfortunately
setting the crashkernel parameter requires editing /etc/grub.d/10_linux
directly and can not
Looking further this memory problem is already tracked in bug #785394,
untouched for almost two years now.
So this bug here should serve as a reminder that the official
documentation (https://help.ubuntu.com/lts/serverguide/kernel-crash-
dump.html) is wrong. It should at least contain links to
