Just found something interesting. Based on the logs from the serial port. This system works fine:
"PeiInstallPeiMemory MemoryBegin 0x93D50000, MemoryLength 0xA2B0000 Temp Stack : BaseAddress=0x400000 Length=0x80000 Temp Heap : BaseAddress=0x480000 Length=0x80000 Total temporary memory: 1048576 bytes. temporary memory stack ever used: 524288 bytes. temporary memory heap used: 63304 bytes. Old Stack size 524288, New stack size 524288 Stack Hob: BaseAddress=0x93D50000 Length=0x80000 Heap Offset = 0x93950000 Stack Offset = 0x93950000 Loading PEIM at 0x0009DFF4000 EntryPoint=0x0009DFF4260 PeiCore.efi" ... "CoreInitializeMemoryServices: BaseAddress - 0x93DE1000 Length - 0x8135000 MinimalMemorySizeNeeded - 0x5AC0000" This one is bricked: "PeiInstallPeiMemory MemoryBegin 0x9C9000, MemoryLength 0x9D637000 Temp Stack : BaseAddress=0x400000 Length=0x80000 Temp Heap : BaseAddress=0x480000 Length=0x80000 Total temporary memory: 1048576 bytes. temporary memory stack ever used: 524288 bytes. temporary memory heap used: 63304 bytes. Old Stack size 524288, New stack size 524288 Stack Hob: BaseAddress=0x9C9000 Length=0x80000 Heap Offset = 0x5C9000 Stack Offset = 0x5C9000 Loading PEIM at 0x0009DFF4000 EntryPoint=0x0009DFF4260 PeiCore.efi" ... "CoreInitializeMemoryServices: BaseAddress - 0x0 Length - 0x0 MinimalMemorySizeNeeded - 0x98E47000 " ... "ASSERT_EFI_ERROR (Status = Out of Resources) ASSERT [DxeCore] ...\MdeModulePkg\Core\Dxe\DxeMain\DxeMain.c(299): !EFI_ERROR (Status) AllocatePoolPages: failed to allocate 1 pages AllocatePool: failed to allocate 120 bytes" It's really strange that the "Stack Hob base address" is so different, and the "MemoryBegin" also. This is making the memory to be detected incorrectly as far as I could understand. So CoreInitializeMemoryServices does not have enougth memory to work on. Any idea about what could cause this difference? Unfortunately I don't have the system in hands. And also cannot share the entire log due to legal. But these are the differences between the bricked system and the normal one. Any idea? Thanks and Regards Rafael R. Machado Em qui, 2 de ago de 2018 às 16:02, Rafael Machado < [email protected]> escreveu: > Hi Laszlo > > Got your point. Thanks for the comment. > > I'll keep working on it. > In case someone has some other information or idea feel free to share. > > Thanks > Rafael > > Em qui, 2 de ago de 2018 às 14:48, Laszlo Ersek <[email protected]> > escreveu: > >> On 08/02/18 18:42, Rafael Machado wrote: >> > Thanks Andrew and Laszlo for the clarification and guidance. >> > >> > About Laszlo questions >> > >> >> Is the reboot automatic (from the platform firmware), or application / >> >> user initiated? >> > Yes. We just do some clean up, finish the events and "return >> EFI_SUCCESS;" >> >> That's really strange. I don't think that's valid or expected behavior. >> If a boot option exits with success, then, as I understand it, the boot >> manager is expected to return to the setup UI at once. (I don't have a >> reference ready for this, but I remember someone mentioning it.) Boot >> option processing continues only if the current boot option exits with >> failure. >> >> I think the reboot you see is actually a crash. (Not saying that the >> issue is in your application, just that the reboot should not be >> triggered by either the application or the platform firmware.) >> >> Thanks, >> Laszlo >> > _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
