Bug 587750 - kdump fails to start on x86_64
Summary: kdump fails to start on x86_64
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools   
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
medium
medium
Target Milestone: ---
Assignee: Neil Horman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 19:10 UTC by Jeff Layton
Modified: 2014-06-18 07:39 UTC (History)
2 users (show)

Fixed In Version: kexec-tools-2.0.0-34.fc13
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-04-30 23:43:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jeff Layton 2010-04-30 19:10:21 UTC
kdump fails to start in F13 on x86_64:

# service kdump start
Starting kdump:                                            [FAILED]

Running kexec manually shows:

# /sbin/kexec -p '--command-line=root=UUID=e070c867-d274-451b-a9db-d889fedebafd ro rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet crashkernel=128M irqpoll maxcpus=1 reset_devices' --initrd=/boot/initrd-2.6.33.2-57.fc13.x86_64kdump.img /boot/vmlinuz-2.6.33.2-57.fc13.x86_64
Can't find kernel text map area from kcore
Cannot load /boot/vmlinuz-2.6.33.2-57.fc13.x86_64

This may be the fix for it:

http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools.git;a=commit;h=c38ad602e15e5c7c4204d1a47e2fd1984cf98afb

Comment 1 Fedora Update System 2010-04-30 19:32:28 UTC
kexec-tools-2.0.0-34.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/kexec-tools-2.0.0-34.fc13

Comment 2 Fedora Update System 2010-04-30 23:43:14 UTC
kexec-tools-2.0.0-34.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.