Bug 283211 - [RHEL5]: Kexec tools should look for a PAE kernel on 32-bit machines with > 4GB memory
Summary: [RHEL5]: Kexec tools should look for a PAE kernel on 32-bit machines with > 4...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kexec-tools
Version: 5.1
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Neil Horman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-07 20:56 UTC by Chris Lalancette
Modified: 2009-03-23 11:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-23 11:53:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Lalancette 2007-09-07 20:56:10 UTC
Description of problem:
If we are running kexec on a 32-bit machine, and
/etc/sysconfig/kdump:KDUMP_KERNELVER is empty, and the machine has memory mapped
above 4GB (you can tell by looking at /proc/iomem), then the kdump init script
should automatically look for a PAE kernel, and then fall back to a non-PAE
kernel if that is not found for the kexec kernel.  The reason for this is the
without the PAE kernel, a machine with > 4G won't be able to dump all of memory.

Comment 1 Neil Horman 2007-09-08 20:12:59 UTC
we should be able to get all of physical memory that the running kernel can
access from the kdump kernel already, without needing to special case PAE.  Do
you have a case in which thats not working?  If so, please provide me a reproducer.

Comment 2 Neil Horman 2008-09-25 12:45:39 UTC
Ping Chris?

Comment 3 Chris Lalancette 2008-09-26 06:23:42 UTC
Neil,
    Oops.  I never looked back at this one, sorry.  I'll have to try again; it certainly may have just been user error.  I'll be away for a week, though, so I won't get back to it until the second week in October, though.  Thanks for the reminder.

Chris Lalancette

Comment 4 Neil Horman 2008-09-26 11:14:41 UTC
well, let me know when you finish retesting.

Comment 5 Neil Horman 2009-03-23 10:59:12 UTC
chris, any update on this?  Its been sitting for some time.

Comment 6 Chris Lalancette 2009-03-23 11:53:10 UTC
Sorry Neil.  I just tried this again, and I couldn't get it to fail; it seems that the kdump script is choosing the correct kernel for all of the cases I can come up with.  I'll close this as NOTABUG.  Thanks for being patient.

Chris Lalancette


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