Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Xishi Qiu <qiuxishi@xxxxxxxxxx>
- Subject: Re: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
- From: Tony Luck <tony.luck@xxxxxxxxx>
- Date: Tue, 19 Feb 2013 13:56:55 -0800
- Cc: Matt Fleming <matt.fleming@xxxxxxxxx>, fenghua.yu@xxxxxxxxx, Liujiang <jiang.liu@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, linux-ia64@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-efi@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, Hanjun Guo <guohanjun@xxxxxxxxxx>, WuJianguo <wujianguo@xxxxxxxxxx>
- In-reply-to: <5113450C.1080109@huawei.com>
- List-id: <linux-ia64.vger.kernel.org>
- References: <51074786.5030007@huawei.com> <1359995565.7515.178.camel@mfleming-mobl1.ger.corp.intel.com> <51131248.3080203@huawei.com> <5113450C.1080109@huawei.com>
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
provide crashkernel
parameters rounded to GRANULE boundaries?
-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]
