Dell - Internal Use - Confidential Thank you Michael,
I recompiled in my lab with these debug options and immediately get a UEFI general protection fault error on the server when booting to that efi file. Could the debug options be making the binary unstable? Lynn Heinemann Principal Engineer, Solutions Support Team Dell EMC| Remote Services and Solutions Office: +1 512 723 7471 lynn.heinem...@dell.com -----Original Message----- From: Michael Brown [mailto:mc...@ipxe.org] Sent: Sunday, January 14, 2018 4:12 PM To: Heinemann, Lynn <lynn_heinem...@dell.com>; ipxe-devel@lists.ipxe.org Subject: Re: [ipxe-devel] iPXE MemoryAllocationLib.c assert failures on Dell PowerEdge On 11/01/18 20:01, lynn.heinem...@dell.com wrote: > I really appreciate the quick reply, no we have not attempted to use the > snponly.efi only the compiled ipxe.efi provided by our end user. To date, > this error has only occurred within the end user environment, I have been > unable to recreate it in my lab. I'm looking for options to increase the > value of our debugging with the end user. The network card being used is a > Dell branded Intel X710 4 port SFP daughter card pci identifier > 8086:1572:1028:0000. The message ASSERT u:\MdePkg\Library\UefiMemoryAllocationLib\MemoryAllocationLib.c(819): !EFI_ERROR (Status) is coming from the EDK2 FreePool() function: https://github.com/tianocore/edk2/blob/master/MdePkg/Library/UefiMemoryAllocationLib/MemoryAllocationLib.c#L819 There are only a few places in iPXE that use FreePool(). You can enable debug for all of them using: DEBUG=nii,efi_block,efi_driver,efi_fbcon,efi_local,efi_pci,efi_snp_hii,efi_usb Are you able to provide remote console access to an environment in which the problem can be reproduced? Thanks, Michael _______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
