Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
* Sachin P. Sant <[EMAIL PROTECTED]> [2008-02-05 06:33]: > Bernhard Walle wrote: >> * Vivek Goyal <[EMAIL PROTECTED]> [2008-02-04 19:38]: >> >>> Bernahard, any idea who is the competitor here? >>> >> Hm ..., can you boot the kernel without crashkernel= and provide the >> /proc/iomem? >> > Attached is the /proc/iomem output with and without crashkernel > parameter. Looks ok. In my case when I added the warning message the kernel BSS was too large. But that doesn't seem to be the case here, BSS ends with 9M and you use 16M as start address for the crashkernel. Bernhard pgprEGPyzsIRN.pgp Description: PGP signature
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
* Sachin P. Sant [EMAIL PROTECTED] [2008-02-05 06:33]: Bernhard Walle wrote: * Vivek Goyal [EMAIL PROTECTED] [2008-02-04 19:38]: Bernahard, any idea who is the competitor here? Hm ..., can you boot the kernel without crashkernel= and provide the /proc/iomem? Attached is the /proc/iomem output with and without crashkernel parameter. Looks ok. In my case when I added the warning message the kernel BSS was too large. But that doesn't seem to be the case here, BSS ends with 9M and you use 16M as start address for the crashkernel. Bernhard pgprEGPyzsIRN.pgp Description: PGP signature
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
Sachin P. Sant wrote: Bernhard Walle wrote: * Vivek Goyal <[EMAIL PROTECTED]> [2008-02-04 19:38]: Bernahard, any idea who is the competitor here? Hm ..., can you boot the kernel without crashkernel= and provide the /proc/iomem? Attached is the /proc/iomem output with and without crashkernel parameter. Adding debug gives this extra information. hm, page 02a9d000 reserved twice. crashkernel reservation failed - memory is in use Will try to add more debug statements. Hm . no problem with 2.6.24-mm1. early res: 4 [9dc00-a0bff] EBDA early res: 5 [8000-11fff] PGTABLE Reserving 128MB of memory at 32MB for crashkernel (System RAM: 9088MB) [e200-e21f] PMD ->81000120 on node 0 # cat /proc/iomem .. 008b8000-0099dc8b : Kernel bss 0200-09ff : Crash kernel c7fcae00-c7fcf7ff : ACPI Tables . Thanks -Sachin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
* Vivek Goyal <[EMAIL PROTECTED]> [2008-02-04 19:38]: > > Bernahard, any idea who is the competitor here? Hm ..., can you boot the kernel without crashkernel= and provide the /proc/iomem? Bernhard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
On Mon, Feb 04, 2008 at 09:41:11PM +0530, Sachin P. Sant wrote: > While trying to configure kdump with 2.6.24-rc8-mm1 [ on a x86-64 box ] > i ran into this problem. Here is the snippet from dmesg during the > failure. [ dmesg log attached ] > > early_ioremap(040e, 0002) => -02103442418 > early_iounmap(82a0040e, 0002) > early_ioremap(0009dc00, 1000) => -02102797312 > early_iounmap(82a9dc00, 1000) > crashkernel reservation failed - memory is in use > [e200-e21f] PMD ->81000120 on node 0 > [e220-e23f] PMD ->81000160 on node 0 > [e240-e25f] PMD ->810001a0 on node 0 > [e260-e27f] PMD ->810001e0 on node 0 > > I am using [EMAIL PROTECTED] value for crashkernel parameter. > Hmm..., So somebody has already reserved the memory we are trying to reserve. Bernhard's BOOTMEM_EXCLUSIVE flag is atleast giving the warning otherwise it would have silently created an overlapping reserved memory area. Sachin, can you please put some debugging statements before the calls to reserve_bootmem() in arch/x86 to find out who all are reserving what memory area and then we can nail down the guy who is reserving some memory between 32M and 160M Wished we had some debugging printk statements for reserve_bootmem too (the way we have for early_ioremap and early_iounmap). Bernahard, any idea who is the competitor here? Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
* Vivek Goyal [EMAIL PROTECTED] [2008-02-04 19:38]: Bernahard, any idea who is the competitor here? Hm ..., can you boot the kernel without crashkernel= and provide the /proc/iomem? Bernhard -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
On Mon, Feb 04, 2008 at 09:41:11PM +0530, Sachin P. Sant wrote: While trying to configure kdump with 2.6.24-rc8-mm1 [ on a x86-64 box ] i ran into this problem. Here is the snippet from dmesg during the failure. [ dmesg log attached ] early_ioremap(040e, 0002) = -02103442418 early_iounmap(82a0040e, 0002) early_ioremap(0009dc00, 1000) = -02102797312 early_iounmap(82a9dc00, 1000) crashkernel reservation failed - memory is in use [e200-e21f] PMD -81000120 on node 0 [e220-e23f] PMD -81000160 on node 0 [e240-e25f] PMD -810001a0 on node 0 [e260-e27f] PMD -810001e0 on node 0 I am using [EMAIL PROTECTED] value for crashkernel parameter. Hmm..., So somebody has already reserved the memory we are trying to reserve. Bernhard's BOOTMEM_EXCLUSIVE flag is atleast giving the warning otherwise it would have silently created an overlapping reserved memory area. Sachin, can you please put some debugging statements before the calls to reserve_bootmem() in arch/x86 to find out who all are reserving what memory area and then we can nail down the guy who is reserving some memory between 32M and 160M Wished we had some debugging printk statements for reserve_bootmem too (the way we have for early_ioremap and early_iounmap). Bernahard, any idea who is the competitor here? Thanks Vivek -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [mm] Crashkernel memory reservation fails with 2.6.24-rc8-mm1
Sachin P. Sant wrote: Bernhard Walle wrote: * Vivek Goyal [EMAIL PROTECTED] [2008-02-04 19:38]: Bernahard, any idea who is the competitor here? Hm ..., can you boot the kernel without crashkernel= and provide the /proc/iomem? Attached is the /proc/iomem output with and without crashkernel parameter. Adding debug gives this extra information. hm, page 02a9d000 reserved twice. crashkernel reservation failed - memory is in use Will try to add more debug statements. Hm . no problem with 2.6.24-mm1. early res: 4 [9dc00-a0bff] EBDA early res: 5 [8000-11fff] PGTABLE Reserving 128MB of memory at 32MB for crashkernel (System RAM: 9088MB) [e200-e21f] PMD -81000120 on node 0 # cat /proc/iomem .. 008b8000-0099dc8b : Kernel bss 0200-09ff : Crash kernel c7fcae00-c7fcf7ff : ACPI Tables . Thanks -Sachin -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
