Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uefi-sct/SctPkg: Memory Allocation Failure on EDK2 stable202411 #236

Open
r1chard-lyu opened this issue Dec 24, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@r1chard-lyu
Copy link

r1chard-lyu commented Dec 24, 2024

While executing the UEFI SCT test (sct.efi) on the edk2-stable202411, the system encounters a memory allocation failure, preventing the sct application from starting properly. This issue results in an assertion failure in Pool.c at line 721, interrupting the test execution.

FSOpen: Open '\X64\sct.EFI' Success
[Security] 3rd party image[0] can be loaded after EndOfDxe: PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)/HD(1,MBR,0xBE1AFDFA,0x3F,0xFBFC1)/\X64\sct.EFI.
None of Tcg2Protocol/CcMeasurementProtocol is installed.
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 61E1040
Loading driver at 0x000060AE000 EntryPoint=0x000060CB81F SCT.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 6219998
ProtectUefiImageCommon - 0x61E1040
  - 0x00000000060AE000 - 0x0000000000036A00
InstallProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA 7E7E428
AllocatePoolPages: failed to allocate 64765 pages
AllocatePool: failed to allocate 265275784 bytes
ASSERT Pool.c(721): Head->Signature == ((('p') | ('h' << 8)) | ((('d') | ('0' << 8)) << 16)) || Head->Signature == ((('p') | ('h' << 8)) | ((('d') | ('1' << 8)) << 16))    
@edhay
Copy link
Contributor

edhay commented Feb 6, 2025

@r1chard-lyu
Thank you for raising this issue.
The issue itself may not be related to edk2-stable202411 and may in fact be a driver issue.

The next steps to narrow down the cause is to check the code after the
InstallProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA 7E7E428

@anncheng-arm to coordinate with @r1chard-lyu and update.

@edhay edhay added the bug Something isn't working label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants