Red Hat Bugzilla – Bug 429014
[RHEL5.2 kdump] ia64 systems unable to boot into kdump kernel
Last modified: 2008-05-21 11:23:16 EDT
Description of problem:
The update from kexec-tools 1.101 + our myriad of patches to tracking the
upstream-ier kexec-tools testing tree has left ia64 systems unable to use kdump.
The crash kernel loads fine, but systems simply hang when they should be booting
into the kdump kernel.
Version-Release number of selected component (if applicable):
Set up kdump on ia64, echo c > /proc/sysrq-trigger
The latest ia64 5.2 beta kernels still kdump just fine with the 5.1 kexec-tools.
I'm currently trying an upstream tree to see if latest kerenls can boot ia64 via
Upstream kernels seem to be doa with our kexec-tools as well. Tring the latest
kexec-tools git tree
note to self: replacing common kexec-elf* files in kexec subdir from 1.101 to
1.02pre fixes this. I'll need to investigate further.
I've noted two things today. I can build locally and produce a working kexec
binary that successfully boots a kdump kernel if:
1) I change build_mem_notes to return -1 if any elf headers we read in are
2) If I don't install the latest elfutils-devel-static on the local system
I have no idea why this works yet.
correction, apparently the actual problem is with the %configure script for the
srpm . If I forgo the %configure sciprt, and just use ./configure instead, the
rpm built locally works fine.
Narrowing it down further, it appears that the default values for $RPM_OPT_FLAGS
seem to be having an adverse affect on the build for ia64.
Fixed in kexe-tools-1.102pre-8.1, on my private pre53 branch. I'll merge when
we open for 5.3 checkins.
good point, I misread what version we were shipping in the initial report.
setting exception flag.
QE ack for RHEL5.2. This is a regression relative to 5.1 and would seriously
impact customer's ability to debug problems in addition to their ability to
provide us with debugging information.
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being marked as a blocker for this release.
Please resolve ASAP.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.