I am encountering repeated warm resets in my UEFI firmware after integrating DpDynamicLib (i.e., enabling the performance measurement features so that the "dp" command can be used in the UEFI Shell).
My platform is built on EDKII. I enabled performance measurement (PERFORMANCE_MEASUREMENT_ENABLE = TRUE) and linked DpDynamicLib so I can collect and view performance data with the "dp" shell command. After adding DpDynamicLib and rebuilding, the firmware enters a loop of warm resets. I traced the issue to a variable named MemoryTypeInformationModified in MdeModulePkg/Library/UefiBootManagerLib. Each boot detects changes in memory usage, sets MemoryTypeInformationModified to TRUE, attempts to update the MemoryTypeInformation UEFI variable, and triggers a warm reset. On the next boot, the same process repeats, causing an endless warm reset loop while trying to enter UEFI Shell. If I manually force MemoryTypeInformationModified = FALSE , the resets stop, but this obviously bypasses the memory type info update and is not a viable long-term fix. I need help determining why the firmware continuously sees changes in memory usage related to performance library allocations and how to finalize or persist an updated MemoryTypeInformation so that it does not force a warm reset on every boot. Specifically, is there a recommended workaround or known fix so that enabling performance measurement does not continually alter the memory allocation profile in a way that the firmware cannot reconcile? -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#121139): https://edk2.groups.io/g/devel/message/121139 Mute This Topic: https://groups.io/mt/111354659/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
