Description of problem: The kdump crash kernel panics when it tries to reserve the MP Config tables on an ES7000. The MP Config table is located above 1MB of physical memory in a reserved memory area. It is located outside the first 1MB area because the tables are too large, 240k. The crash kernel is given a user defined memory map with E820 reserved and ACPI areas passed in by kexec tools and a usable area from 16MB physical to 80MB physical. This user defined map causes the top of memory to be set as 80MB. The ACPI tables and MP Tables reside higher in memory. When reserving memory with reserve_bootmem_generic, the function has a BUG panic if the memory location to reserve is above the top of usable memory for the node. The MP table is above the top of memory in a user defined memory map. Version-Release number of selected component (if applicable): Tested with RHEL5 Beta 2 Milestone 9 How reproducible: Always on an ES7000 Steps to Reproduce: 1. Setup for kdump with boot paramter crashkernel=64M@16M 2. Install the kernel with kexec -p /boot/vmlinux-kdump --args-linux --command-line="`cat /proc/cmdline` lpj=1306000 earlyprintk=serial,ttyS0,115200n8" --initrd=/boot/initrd-kdump 3. Issue alt-sysrq-c (or echo c > /proc/sysrq-trigger) Actual results: Actual kernel panic to follow Expected results: Kdump kernel should boot up. Additional info: http://www.ussg.iu.edu/hypermail/linux/kernel/0611.0/0796.html The associated patch is currently in 2.6.19-rc5-mm1
Created attachment 141102 [details] This patch will avoid any attempts to reserve memory about end_pfn_map, the end of memory
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
FYI, this patch has been accepted into 2.6.19-rc6
in 2.6.18-1.2789.el5
Is this kernel available for download & testing, or do we need to wait for the next release?
A package has been built which should help the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.