Ubuntu
linux package

crashkernel memory reservation ignored

Bug #364414 reported by Jamin W. Collins on 2009-04-21

32

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	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://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe). However, attempting to execute the kexec command results in an error that the crashkernel memory has not been reserved. Near as I can tell, the kernel parameters are correct.

# grep 'Command line:' /var/log/dmesg
[ 0.000000] Command line: root=UUID=66cf90ad-d4ec-4ec1-afb0-3fc3b17e3141 ro vga=0x37d quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M

# uname -r
2.6.28-11-generic

# kexec -p /boot/vmlinuz-2.6.28-11-generic --initrd=/boot/initrd.img-2.6.28-11-generic --append=root=UUID=66cf90ad-d4ec-4ec1-afb0-3fc3b17e3141 irqpoll maxcpus=1
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
NonfreeKernelModules: nvidia ath_hal
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=66cf90ad-d4ec-4ec1-afb0-3fc3b17e3141 ro vga=0x37d quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux

Tags:

Related branches

lp:~ubuntu-core-dev/grub/ubuntu

lp:ubuntu/lucid/grub

Revision history for this message

Jamin W. Collins (jcollins) wrote on 2009-04-21:

#1

BootDmesg.txt Edit (61.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (850 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (990 bytes, text/plain; charset="utf-8")
HalComputerInfo.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (509 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Irfan Adilovic (irfy) wrote on 2009-05-11:

#2

I am observing the exact same behavior. Same crashkernel argument, same kernel, same arch, same distro, also nvidia nonfree kernel module.

Revision history for this message

Stanislaw Pitucha (viraptor-gmail) wrote on 2009-05-16:

#3

Same here. Is there any specific data I should report?

Revision history for this message

Kings (kingslee) wrote on 2009-06-16:

#4

I get such message "Memory for crashkernel is not reserved" everytime I boot.

kernel argument ro vga=795 crashkernel=384M-2G:64M@16M,2G-:128M@16M, also nvidia nonfree kernel module, using "server" "Linux server1 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux" kernel

Revision history for this message

phirestalker (firestalker1-deactivatedaccount) wrote on 2009-07-16:

#5

me too
root=UUID=66252ae1-96e2-4f6b-bfd3-f8194579fa34 ro splash crashkernel=384M-2G:64M@16M,2G-:128M@16M

Revision history for this message

phirestalker (firestalker1-deactivatedaccount) wrote on 2009-07-16:

#6

oh but I don't have any proprietary drivers installed

Revision history for this message

Duane Waddle (duane-waddle) wrote on 2009-08-22:

#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.

Revision history for this message

Andy Whitcroft (apw) wrote on 2009-09-15:

#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=384M-2G:64M,2G-:128M

Changed in linux (Ubuntu):
assignee:	nobody → Andy Whitcroft (apw)
importance:	Undecided → Low
status:	New → In Progress
status:	In Progress → Incomplete

Revision history for this message

Duane Waddle (duane-waddle) wrote on 2009-09-17:

#9

Andy's suggestion of "crashkernel=384M-2G:64M,2G-:128M" gets me a proper reservation on 2.6.28-15-generic.

Sep 17 16:21:03 localhost kernel: [ 0.000000] Reserving 128MB of memory at 32MB for crashkernel (System RAM: 3062MB)

Andy Whitcroft (apw) on 2010-06-18

Changed in linux (Ubuntu):
assignee:	Andy Whitcroft (apw) → nobody

Revision history for this message

Jamin W. Collins (jcollins) wrote on 2010-06-22:

#10

Looks like Lucid gets the reservation correct (crashkernel=384M-2G:64M,2G-:128M) as I see the following:

[ 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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.