Re: [edk2] Hang when calling ExitBootServices on IA32 firmware v1.0 on MinnowBoard Turbot
Hi Rebecca, MinnowBoard Turbot Dual Ethernet runs with UDK2018 https://github.com/MinnowWare/UDK2018-MinnowBoard That BIOS starts a 64Bit Windows10, including S3 and resumeā¦ Phil From: edk2-devel on behalf of Rebecca Cran via edk2-devel Sent: Wednesday, February 27, 2019 12:00:45 AM To: edk2-devel@lists.01.org Subject: Re: [edk2] Hang when calling ExitBootServices on IA32 firmware v1.0 on MinnowBoard Turbot On 2/25/19 5:08 PM, Rebecca Cran via edk2-devel wrote: > I've been trying to test a boot loader on my MinnowBoard Turbot board. > It's running the latest 1.0 firmware from firmware.intel.com, and I'm > seeing a hang at the point when gBS->ExitBootServices is called. I did more debugging using OVMF and found that the i386 boot loader code was trying to call printf (which allocates memory) after ExitBootServices. And that booting an i386 kernel isn't actually supported. So there's not a problem with the MinnowBoard firmware. -- Rebecca Cran ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] Hang when calling ExitBootServices on IA32 firmware v1.0 on MinnowBoard Turbot
On 2/25/19 5:08 PM, Rebecca Cran via edk2-devel wrote: I've been trying to test a boot loader on my MinnowBoard Turbot board. It's running the latest 1.0 firmware from firmware.intel.com, and I'm seeing a hang at the point when gBS->ExitBootServices is called. I did more debugging using OVMF and found that the i386 boot loader code was trying to call printf (which allocates memory) after ExitBootServices. And that booting an i386 kernel isn't actually supported. So there's not a problem with the MinnowBoard firmware. -- Rebecca Cran ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
[edk2] Hang when calling ExitBootServices on IA32 firmware v1.0 on MinnowBoard Turbot
I've been trying to test a boot loader on my MinnowBoard Turbot board. It's running the latest 1.0 firmware from firmware.intel.com, and I'm seeing a hang at the point when gBS->ExitBootServices is called. The last debug output is: ConfigSccBootableDevicesAtExitBootService() End SetUefiImageMemoryAttributes - 0x787EB000 - 0x4000 (0x0008) SetUefiImageMemoryAttributes - 0x787E8000 - 0x3000 (0x0008) SetUefiImageMemoryAttributes - 0x787E5000 - 0x3000 (0x0008) SetUefiImageMemoryAttributes - 0x787E1000 - 0x4000 (0x0008) SetUefiImageMemoryAttributes - 0x787DB000 - 0x6000 (0x0008) SetUefiImageMemoryAttributes - 0x787D5000 - 0x6000 (0x0008) SetUefiImageMemoryAttributes - 0x787CC000 - 0x9000 (0x0008) SetUefiImageMemoryAttributes - 0x787C6000 - 0x6000 (0x0008) SetUefiImageMemoryAttributes - 0x787C3000 - 0x3000 (0x0008) SetUefiImageMemoryAttributes - 0x787BD000 - 0x6000 (0x0008) SetUefiImageMemoryAttributes - 0x787B8000 - 0x5000 (0x0008) SetUefiImageMemoryAttributes - 0x787B2000 - 0x6000 (0x0008) SetUefiImageMemoryAttributes - 0x787AC000 - 0x6000 (0x0008) SetUefiImageMemoryAttributes - 0x787A9000 - 0x3000 (0x0008) SetUefiImageMemoryAttributes - 0x787A5000 - 0x4000 (0x0008) SetUefiImageMemoryAttributes - 0x787A2000 - 0x3000 (0x0008) SetUefiImageMemoryAttributes - 0x7879F000 - 0x3000 (0x0008) The X64 firmware works fine: the boot loader finishes and the kernel starts running. I looked to see where ConfigSccBootableDevicesAtExitBootService might be, and unfortunately it seems it's in one of the binary modules. The code for the boot loader is in https://svnweb.freebsd.org/base/head/stand/efi/loader/bootinfo.c?revision=338022=markup . -- Rebecca Cran ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel