[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D0D2CA1.6070502@kernel.org>
Date: Sat, 18 Dec 2010 13:50:25 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Stanislaw Gruszka <sgruszka@...hat.com>
CC: "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Vivek Goyal <vgoyal@...hat.com>,
Maxim Uvarov <muvarov@...il.com>, linux-kernel@...r.kernel.org,
Neil Horman <nhorman@...hat.com>
Subject: Re: kdump broken on 2.6.37-rc4
On 12/16/2010 02:00 AM, Stanislaw Gruszka wrote:
> On Wed, Dec 15, 2010 at 08:29:01PM -0800, Yinghai Lu wrote:
>> please check
>>
>> [PATCH] x86, crashkernel, 32bit: only try to get range under 512M
>>
>> Steanishlaw report kdump is 32bit is broken.
> LOL
>
>> in misc.c for decompresser, it will do sanity checking to make sure heap
>> heap under 512M.
>>
>> So limit it in first kernel under 512M for 32bit system.
>>
>> Reported-by: Stanislaw Gruszka <sgruszka@...hat.com>
>> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>
> Patch fix problem on my T-60 laptop.
>
> As expected patch does not help on my other T-500 x86_64 system,
> kdump not work there, but perhaps this is a different problem,
> I'm going to check it.
Can you try crashkernel=256M@...M on your T-500 x86_64 system?
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists