Red Hat Bugzilla – Bug 179475
kdump service fails to start
Last modified: 2007-11-30 17:11:22 EST
Description of problem: I tried to follow the instructions at http://fedoranews.org/mediawiki/index.php/Using_Kexec_and_Kdump_in_Rawhide for using kdump to debug kernel crashes. However after installing kexec-tools, the kdump service fails to start giving this message: Invalid memory segment 0x1000000 - 0x1242fff Version-Release number of selected component (if applicable): kexec-tools-1.101-5.1 How reproducible: always Steps to Reproduce: 1. install kexec-tools 2. start kdump service 3. Actual results: kdump service doesn't start Expected results: kdump starts Additional info:
Almost same error here, but with slightly newer build of kexec-tools. I get: Invalid memory segment 0x1000000 - 0x1240fff Version-Release number of selected component (if applicable): kexec-tools-1.101-7.1 kernel-2.6.15-1.1907_FC5 kernel-kdump-2.6.15-1.1907_FC5 Additional info: System is fairly fresh, installed from FC5T2 and updated to current rawhide. Kernel is not tainted. $ cat /etc/sysconfig/kdump # Kernel Version string for the -kdump kernel, such as 2.6.13-1544.FC5kdump # If no version is specified, then the init script will try to find a # kdump kernel with the same version number as the running kernel. KDUMP_KERNELVER="" # The kdump commandline is the command line that needs to be passed off to # the kdump kernel. This will likely match the contents of the grub kernel # line. For example: # KDUMP_COMMANDLINE="ro root=LABEL=/" # If a command line is not specified, the default will be taken from # /proc/cmdline KDUMP_COMMANDLINE="" # Any additional kexec arguments required. In most situations, this should # be left empty KEXEC_ARGS="" $ cat /proc/cmdline ro root=LABEL=/1 $ uname -a Linux ip70-171-208-137.tc.ph.cox.net 2.6.15-1.1907_FC5 #1 Fri Feb 3 23:23:13 EST 2006 i686 athlon i386 GNU/Linux
*** Bug 182688 has been marked as a duplicate of this bug. ***
The documentation is unfortunately a little dated. Please add the kernel parameter "crashkernel =64M@16M" to your /etc/grub.conf file in the kernel you are using as shown in the example below: kernel /vmlinuz-2.6.15-1.2039_FC5 ro root=LABEL=/ crashkernel=64M@16M Then reboot your machine. This parameter tells the kernel to reserve 64MB of memory at physical location 16MB. The kdump kernel is placed here upon completion of the kdump init script. Also please update your kexec_tools package (yum update kexec_tools). A few bugs fixes have been added to make this process easier. Let me know if this solves your problem.
We could definitely use a kdump howto. :) /me ponders writing one up to put in the Fedora wiki...