Re: crash dump memory reservation regression
From: Cong Wang
Date: Mon Mar 26 2012 - 06:32:00 EST
On Tue, Mar 13, 2012 at 1:31 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> On Sun, Mar 11, 2012 at 8:00 PM, CAI Qian <caiqian@xxxxxxxxxx> wrote:
>> commit 3661ca66a42e306aaf53246fb75aec1ea01be0f0
>> x86, memblock: Fix crashkernel allocation
>> introduced a regression that crashkernel=512M
>> according to bisecting will fail like this,
>> crashkernel reservation failed - No suitable area found.
>> The full dmesg can be found here.
> The reason is: we put pagetable for [0,2g) just blow 512M.
> Later we have other patches that will put pagetable for [0,2g) just
> below 2g. even at that time we only can access 512M, because we use
> early_ioremap to access page table.
> But that good_end part get reverted in following because it cause s4
> resume fail.
> So there will be pagetable around just below 512M again. So you have
> no chance to get 512M below 768M.
> Solution will be:
> 1. Âremove the good_end setting for 64 bit again. and root cause S4 resume.
> 2. Âget page low?
> 3. Âfix kdump, and make kdump could take two ranges, one is small
> segment below 512M, other part could be more than 4G.
Is increasing CRASH_KERNEL_ADDR_MAX a 4th solution? I know we need
to fix kexec-tools too, but we will get more benefits...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/