On Tue, Feb 19, 2013 at 5:38 PM, Xishi Qiu qiuxi...@huawei.com wrote:
Seems like a good idea, should we modify
\linux\Documentation\kernel-parameters.txt?
Perhaps in Documentation/kdump/kdump.txt (which the crashkernel entry
in kernel-parameters.txt
points at). The ia64 section of kdump.txt
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
N�r��yb�X��ǧv�^�){.n�+{�y^n�r���z���h���
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
On 2013/2/13 18:07, Matt Fleming wrote:
In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set
crashkernel=1024M-:600M
and use sparse memory model, when crash kernel booting it changes
[128M-728M] to [128M-720M].
But initrd memory is in [709M-727M], and virt_addr_valid() *can not*
On Tue, 12 Feb 2013 16:11:33 -0800
Tony Luck tony.l...@gmail.com wrote:
Building linux-next today (tag next-20130212) I get the following errors when
building arch/ia64/configs/{tiger_defconfig, zx1_defconfig, bigsur_defconfig,
sim_defconfig}
arch/ia64/mm/init.c: In function
On Tue, 12 Feb 2013 16:11:33 -0800
Tony Luck tony.l...@gmail.com wrote:
Building linux-next today (tag next-20130212) I get the following errors when
building arch/ia64/configs/{tiger_defconfig, zx1_defconfig, bigsur_defconfig,
sim_defconfig}
arch/ia64/mm/init.c: In function
