crashkernel memory reservation ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
Low
|
Unassigned |
Bug Description
In attempting to track down a rather elusive kernel panic I've begun trying to use the kdump facility based on information found here (https:/
# grep 'Command line:' /var/log/dmesg
[ 0.000000] Command line: root=UUID=
# uname -r
2.6.28-11-generic
# kexec -p /boot/vmlinuz-
Memory for crashkernel is not reserved
Please reserve memory by passing "crashkernel=X@Y" parameter to the kernel
Then try loading kdump kernel
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: LENOVO
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux
Jamin W. Collins (jcollins) wrote : | #1 |
Irfan Adilovic (irfy) wrote : | #2 |
Stanislaw Pitucha (viraptor-gmail) wrote : | #3 |
Same here. Is there any specific data I should report?
Kings (kingslee) wrote : | #4 |
I get such message "Memory for crashkernel is not reserved" everytime I boot.
kernel argument ro vga=795 crashkernel=
me too
root=UUID=
oh but I don't have any proprietary drivers installed
Duane Waddle (duane-waddle) wrote : | #7 |
I've seen the same thing on my x86 Jaunty - updating the grub menu.lst to where the argument for crashkernel is just "crashkernel=128M" seems to fix the reservation problem.
Andy Whitcroft (apw) wrote : | #8 |
On my current setup this is using the following incantion, note that it does not specify the location, can you see if that helps:
crashkernel
Changed in linux (Ubuntu): | |
assignee: | nobody → Andy Whitcroft (apw) |
importance: | Undecided → Low |
status: | New → In Progress |
status: | In Progress → Incomplete |
Duane Waddle (duane-waddle) wrote : | #9 |
Andy's suggestion of "crashkernel=
Sep 17 16:21:03 localhost kernel: [ 0.000000] Reserving 128MB of memory at 32MB for crashkernel (System RAM: 3062MB)
Changed in linux (Ubuntu): | |
assignee: | Andy Whitcroft (apw) → nobody |
Jamin W. Collins (jcollins) wrote : | #10 |
Looks like Lucid gets the reservation correct (crashkernel=
[ 0.000000] Reserving 128MB of memory at 32MB for crashkernel (System RAM: 9152MB)
Additionally, my system has now been generating crash dumps (and rebooting) instead of simply freezing.
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
I am observing the exact same behavior. Same crashkernel argument, same kernel, same arch, same distro, also nvidia nonfree kernel module.