From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xishi Qiu Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting Date: Wed, 20 Feb 2013 09:38:16 +0800 Message-ID: <51242908.2050308@huawei.com> References: <51074786.5030007@huawei.com> <1359995565.7515.178.camel@mfleming-mobl1.ger.corp.intel.com> <51131248.3080203@huawei.com> <5113450C.1080109@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org To: Tony Luck Cc: Matt Fleming , fenghua.yu@intel.com, Liujiang , Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, linux-mm@kvack.org, Hanjun Guo , WuJianguo List-Id: linux-efi@vger.kernel.org On 2013/2/20 5:56, Tony Luck wrote: > Foolishly sent an earlier reply from Outlook which appears > to have mangled/lost it. Trying again ... > >> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M" > > Is this where the real problem begins? Should we insist that users Hi Tony, I think this is the real problem begins and it only appears when use Sparse-Memory. > provide crashkernel > parameters rounded to GRANULE boundaries? > Seems like a good idea, should we modify "\linux\Documentation\kernel-parameters.txt"? Thanks, Xishi Qiu > -Tony > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xishi Qiu Date: Wed, 20 Feb 2013 01:38:16 +0000 Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting Message-Id: <51242908.2050308@huawei.com> List-Id: References: <51074786.5030007@huawei.com> <1359995565.7515.178.camel@mfleming-mobl1.ger.corp.intel.com> <51131248.3080203@huawei.com> <5113450C.1080109@huawei.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Tony Luck Cc: Matt Fleming , fenghua.yu@intel.com, Liujiang , Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, linux-mm@kvack.org, Hanjun Guo , WuJianguo On 2013/2/20 5:56, Tony Luck wrote: > Foolishly sent an earlier reply from Outlook which appears > to have mangled/lost it. Trying again ... > >> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel24M-:600M" > > Is this where the real problem begins? Should we insist that users Hi Tony, I think this is the real problem begins and it only appears when use Sparse-Memory. > provide crashkernel > parameters rounded to GRANULE boundaries? > Seems like a good idea, should we modify "\linux\Documentation\kernel-parameters.txt"? Thanks, Xishi Qiu > -Tony > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758995Ab3BTBim (ORCPT ); Tue, 19 Feb 2013 20:38:42 -0500 Received: from szxga01-in.huawei.com ([119.145.14.64]:2540 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757174Ab3BTBik (ORCPT ); Tue, 19 Feb 2013 20:38:40 -0500 Message-ID: <51242908.2050308@huawei.com> Date: Wed, 20 Feb 2013 09:38:16 +0800 From: Xishi Qiu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Tony Luck CC: Matt Fleming , , Liujiang , Andrew Morton , , , , , Hanjun Guo , WuJianguo Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting References: <51074786.5030007@huawei.com> <1359995565.7515.178.camel@mfleming-mobl1.ger.corp.intel.com> <51131248.3080203@huawei.com> <5113450C.1080109@huawei.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.135.74.196] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2013/2/20 5:56, Tony Luck wrote: > Foolishly sent an earlier reply from Outlook which appears > to have mangled/lost it. Trying again ... > >> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M" > > Is this where the real problem begins? Should we insist that users Hi Tony, I think this is the real problem begins and it only appears when use Sparse-Memory. > provide crashkernel > parameters rounded to GRANULE boundaries? > Seems like a good idea, should we modify "\linux\Documentation\kernel-parameters.txt"? Thanks, Xishi Qiu > -Tony >