Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 283191

Summary: [RHEL5]: Xen kexec very often fails to succeed on certain hardware (HPET?)
Product: Red Hat Enterprise Linux 5 Reporter: Chris Lalancette <clalance>
Component: kernel-xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED DUPLICATE QA Contact: Martin Jenner <mjenner>
Severity: low Docs Contact:
Priority: medium    
Version: 5.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-22 08:41:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Full output from the hang after a kexec
none
dmidecode from the machine that won't kexec reliably none

Description Chris Lalancette 2007-09-07 20:51:33 UTC 
Description of problem:

When using kdump on Xen kernels on certain pieces of hardware, I very often fail
the kexec.  In particular, what happens is that I "echo c >
/proc/sysrq-trigger", the kexec kernel starts to come up, and then just hangs
around forever "Using HPET for base-timer" (I'll upload the complete log). 
Sometimes it doesn't hang, but most times it actually does.

I'll also attach more information about the hardware, but it is an AMD system
with 8GB of RAM, running the 2.6.18-45.el5xen 32-bit kernel.  The grub.conf
entry is:

title Red Hat Enterprise Linux Server (2.6.18-45.el5.bz251341_chrisxen)
        root (hd0,0)
        kernel /xen.gz-2.6.18-45.el5 com1=115200,8n1 crashkernel=128M@32M
        module /vmlinuz-2.6.18-45.el5xen ro root=/dev/VolGroup00/LogVol00
console=tty0 console=ttyS0,115200
        module /initrd-2.6.18-45.el5xen.img
Comment 1 Chris Lalancette 2007-09-07 20:51:33 UTC 
Created attachment 190491 [details]
Full output from the hang after a kexec
Comment 2 Chris Lalancette 2007-09-07 20:52:09 UTC 
Created attachment 190501 [details]
dmidecode from the machine that won't kexec reliably
Comment 3 Stephen Tweedie 2007-09-10 12:58:19 UTC 
> with 8GB of RAM

In that case, does it help if you use the PAE kernel for the kdump?
Comment 4 Chris Lalancette 2009-01-22 08:41:14 UTC 
Probably another dup of 473038.  Closing it as such.

Chris Lalancette

*** This bug has been marked as a duplicate of bug 473038 ***