On Mon, Oct 28, 2013 at 09:18:24AM +0800, Dave Young wrote: > There should be some people see below message with non-kexec kernel: > "Could not reserve boot range ..." I can find one other report like that: https://lkml.org/lkml/2013/7/16/309 [ 0.000000] efi: Could not reserve boot range [0x0000000000-0x0000000fff] for efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000001000) (0MB) which is EFI_BOOT_SERVICES_CODE and efi: Could not reserve boot range [0x000005f000-0x000009ffff] for efi: mem06: type=3, attr=0xf, range=[0x000000000005f000-0x00000000000a0000) (0MB) which is of the same type. > But it's hard for them to notice the bad functionality because > it's only one mem range which might be not the boot range what > SetVirtualAddressMap need Right. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
