Messages in this thread | | | Date | Wed, 31 Jul 2013 21:58:58 +0100 | From | Matthew Garrett <> | Subject | Re: Corrupted EFI region |
| |
On Wed, Jul 31, 2013 at 10:54:31PM +0200, Borislav Petkov wrote:
> efi: mem08: type=7, attr=0xf, range=[0x0000000040000000-0x000000007c000000) (960MB) > efi: mem09: type=4, attr=0xf, range=[0x000000007c000000-0x000000007c020000) (0MB) > efi: mem10: type=7, attr=0xf, range=[0x000000007c020000-0x000000007e0ad000) (32MB) > -efi: mem11: type=4, attr=0xf, range=[0x000000007e0ad000-0x000000007e0cc000) (0MB) > +efi: mem11: type=4, attr=0xf, range=[0x000000007e0ad000-0x000000007e0ad000) (0MB) > efi: mem12: type=7, attr=0xf, range=[0x000000007e0cc000-0x000000007e0cd000) (0MB) > efi: mem13: type=4, attr=0xf, range=[0x000000007e0cd000-0x000000007e55d000) (4MB) > efi: mem14: type=3, attr=0xf, range=[0x000000007e55d000-0x000000007e59c000) (0MB)
Are we making any EFI calls in between? I certainly wouldn't expect the memory map to change after ExitBootServices, but up until that point the firmware's free to mess with it.
-- Matthew Garrett | mjg59@srcf.ucam.org
| |