# Troubleshoot using UEFI log The UEFI log provides information about the start and end of UEFI. The table lists the log entries that can help you verify the start and end of UEFI. Table : Checking UEFI log | Log entry | Description | | --- | --- | | `UEFI Start [ 1568]` | Indicates the start of UEFI | | `[ 3086] UEFI End` | Indicates the end of UEFI | Note The numbers in the log entry column of the table show the timestamp in milliseconds. The following example log uses the debug build flavor. To use the build flavor, replace the ‘RELEASE’ string with ‘DEBUG’ in the boot build command. For more information, see [Build BOOT](https://docs.qualcomm.com/doc/80-80022-254/topic/build_addn_info.html#build-firmware). - UEFI Start [ 1568] - 0x09FC01000 [ 1571] Sec.efi ASLR : ON DEP : ON (RTB) Timer Delta : +11 mS RAM Entry 0 : Base 0x0080000000 Size 0x003A800000 RAM Entry 1 : Base 0x00C0000000 Size 0x0040000000 RAM Entry 2 : Base 0x0100000000 Size 0x0100000000 Total Available RAM : 6056 MB (0x017A800000) Total Installed RAM : 6144 MB (0x0180000000) Multithread : ON (Lib ver 1.2) CPU Cores : 8 (init 2) Init 1 aux cores of 7 Init CPU core 1 CONF File : uefiplatLA.cfg UEFI Ver : 6.0.231205.BOOT. Build Info : 64b Boot Device : UFS PROD Mode : FALSE Retail : FALSE Scheduler up on Core 1 DTB config : client[0]..trace[0]..verbose[0] - 0x09F0CF000 [ 1630] DxeCore.efi Loading DxeCore at 0x009F0CF000 EntryPoint=0x009F0D0000 HOBLIST address in DXE = 0x9EEC0018 FV Hob 0x9FC00000 - 0x9FE70FFF FV Hob 0x9F10E000 - 0x9F47AFFF FV2 Hob 0x9F10E000 - 0x9F47AFFF - 631008B0-B2D1-410A-8B49-2C5C4D8ECC7E - 00000000-0000-0000-0000-000000000000 - 0x09F069000 [ 1633] EnvDxe.efi - 0x09F05F000 [ 1634] RscRtDxe.efi - 0x09F057000 [ 1634] SCHandlerRtDxe.efi - 0x09EB94000 [ 1634] RuntimeDxe.efi - 0x09F049000 [ 1635] ArmCpuDxe.efi - 0x09F040000 [ 1636] ArmGicDxe.efi - 0x09F039000 [ 1636] MetronomeDxe.efi - 0x09F031000 [ 1636] ArmTimerDxe.efi - 0x09F027000 [ 1636] SmemDxe.efi - 0x09EFCD000 [ 1637] DALSys.efi - 0x09EFC4000 [ 1637] HWIODxeDriver.efi - 0x09EFB9000 [ 1637] ChipInfo.efi - 0x09EFB1000 [ 1638] PlatformInfoDxeDriver.efi - 0x09EF8D000 [ 1638] HALIOMMU.efi - 0x09EF79000 [ 1687] ULogDxe.efi - 0x09EF71000 [ 1687] CmdDbDxe.efi - 0x09EF69000 [ 1688] PwrUtilsDxe.efi - 0x09EF56000 [ 1688] NpaDxe.efi - 0x09EF46000 [ 1689] RpmhDxe.efi - 0x09EF3A000 [ 1689] VcsDxe.efi - 0x09EF0C000 [ 1690] ClockDxe.efi Cluster 0: 0 Hz Cluster 2: 0 Hz - 0x09EEFF000 [ 1697] ICBDxe.efi - 0x09EEF6000 [ 1699] ShmBridgeDxeLA.efi - 0x09EEE7000 [ 1700] ScmDxeLA.efi - 0x09EEDE000 [ 1702] DALTLMM.efi - 0x09EED4000 [ 1702] SPMI.efi - 0x09EECA000 [ 1707] I2C.efi - 0x09EB8B000 [ 1707] ResetRuntimeDxe.efi - 0x09EB66000 [ 1708] PmicDxe.efi PM0: 47, PM1: 63, PM2: 49, PM8: 46, Module cannot re-initialize DAL module environments - 0x09EB5B000 [ 1726] DiskIoDxe.efi - 0x09EB4E000 [ 1726] PartitionDxe.efi - 0x09EB46000 [ 1726] EnglishDxe.efi - 0x09EB3B000 [ 1727] FvSimpleFileSystem.efi - 0x09EB1F000 [ 1727] SdccDxe.efi - 0x09EAFE000 [ 1728] UFSDxe.efi UFS INQUIRY ID: SAMSUNG KM2L9001CM-B518 0700 UFS Boot LUN: 1 Protective MBR validation might be needed. Protective MBR validation might be needed. - 0x09E80F000 [ 1757] Fat.efi - 0x09D9B0000 [ 1757] TzDxeLA.efi - 0x09D90F000 [ 1759] VariableDxe.efi ConfigStorPartitions: Status:Success variable policy engine disabled - 0x09E807000 [ 1877] QcomWDogDxe.efi HW Wdog Setting from PCD : Disabled - 0x09D927000 [ 1878] WatchdogTimer.efi - 0x09D6D4000 [ 1878] SecurityStubDxe.efi - 0x09E821000 [ 1878] EmbeddedMonotonicCounter.efi - 0x09D91E000 [ 1880] RealTimeClock.efi - 0x09D6AD000 [ 1881] DevicePathDxe.efi - 0x09D6CC000 [ 1881] CapsuleRuntimeDxe.efi - 0x09D666000 [ 1882] HiiDatabase.efi - 0x09D6C3000 [ 1882] FontDxe.efi - 0x09D58E000 [ 1887] QcomBds.efi - 0x09D63F000 [ 1895] VerifiedBootDxe.efi - 0x09D65A000 [ 1896] DDRInfoDxe.efi - 0x09D626000 [ 1897] FeatureEnablerDxe.efi QseeResponse->result = 0xFFFFFFFF Status = 0x7 QseeResponse->result = 0xFFFFFFFF Status = 0x7 Image partition label not found EFI_QseecomStartApp: Load from partition (featenabler_a)Failed: Status(0x800000000000000E), appId(0) QseeResponse->result = 0xFFFFFFFF Status = 0x7 QseeResponse->result = 0xFFFFFFFF Status = 0x7 Image partition label not found EFI_QseecomStartApp: Load from partition (featenabler)Failed: Status(0x800000000000000E), appId(0) Image partition label not found LoadImageFromPartitionUsingGuid Failed: 14 EFI_QseecomStartApp: Load Failed: Status(0x800000000000000E) Failed to start featenabler_a TA, status = 14 - 0x09D4EB000 [ 1901] DisplayDxe.efi DisplayDxe: SW renderer mode enabled! DisplayDxe: Panel ID:0x00000000 [LCD] DisplayDxe: Resolution 640x480 (1 intf) - 0x09D5DA000 [ 1912] FvDxe.efi - 0x09D60B000 [ 1912] PILProxyDxe.efi - 0x09D555000 [ 1913] PILDxe.efi - 0x09D5CF000 [ 1934] IPCCDxe.efi - 0x09D571000 [ 1934] GlinkDxe.efi smem_alloc_ex: SMEM alloc_ex failed with err=-3! smem_type=478, remote=3, size=32, flags=0x40000000. - 0x09D4DB000 [ 1935] CPRDxe.efi - 0x09D586000 [ 1935] PrintDxe.efi - 0x09D540000 [ 1936] SPI.efi - 0x09D4C2000 [ 1936] PmicGlinkDxe.efi - 0x09D4D1000 [ 1937] UsbPwrCtrlDxe.efi - 0x09D483000 [ 1937] QcomChargerDxeLA.efi - 0x09D54D000 [ 1947] ChargerExDxe.efi - 0x09D46A000 [ 1947] UsbfnDwc3Dxe.efi - 0x09D4AB000 [ 1948] XhciPciEmulation.efi - 0x09D43B000 [ 1948] XhciDxe.efi - 0x09D429000 [ 1949] UsbBusDxe.efi - 0x09D41C000 [ 1949] UsbKbDxe.efi - 0x09D4B6000 [ 1950] UsbMassStorageDxe.efi - 0x09D406000 [ 1950] UsbConfigDxe.efi UsbConfigInit: USB RUMI 0, ver 65536, sub 1 UsbConfigLibOpenProtocols: PMI version (0x0) UsbConfigLibOpenProtocols: gPmicNpaClientHS2 cannot be created UsbConfigInit: Dual Role Enabled on Port Number: 0 UsbConfigInit: after setting role UsbConfigInit: UsbConfigInit, not start on port: 0, mode 0 UsbConfigInit: Dual Role Enabled on Port Number: 1 UsbConfigInit: after setting role UsbConfigInit: UsbConfigInit, not start on port: 1, mode 0 UsbConfigInit: UsbPwrCtrl No. of Ports = pinctrl-1 UsbConfigPortsQueryConnectionChange: usbport->connectstate: ATT ConnectSts : Attach, Data Role : UFP (DEVICE Mode), Lane : CC1, CoreNum : 0 HandlePortPartnerXtach: Cable Attach core 0, portmode 1, dual mode 1 - 0x09D455000 [ 1954] ButtonsDxe.efi ButtonsDxeTest: Keypress SDAM data payload 0 - 0x09D462000 [ 1956] TsensDxe.efi - 0x09D3FE000 [ 1958] LimitsDxe.efi - 0x09D3D7000 [ 1962] GpiDxe.efi - 0x09D390000 [ 2010] UCDxe.efi - 0x09D3C6000 [ 2014] RngDxe.efi - 0x09D3BE000 [ 2015] SimpleTextInOutSerial.efi - 0x09D386000 [ 2016] ConPlatformDxe.efi - 0x09D369000 [ 2016] ConSplitterDxe.efi - 0x09D35D000 [ 2017] GraphicsConsoleDxe.efi - 0x09D37C000 [ 2018] ASN1X509Dxe.efi - 0x09D3B3000 [ 2019] SecRSADxe.efi - 0x09D348000 [ 2019] DtPlatformDxe.efi DtPlatformLoadDtb XXXxxxx-rb3.dtb is loaded DtPlatformDxeEntryPoint: no DT/ACPI preference found, defaulting to DTB - 0x09D2A6000 [ 2030] SoftSKUDxe.efi SoftSKUDxeInitialize: SoftSKU not supported for this chip Error: Image at 0009D2A6000 start failed: Unsupported - 0x09D2A6000 [ 2033] MinidumpTADxe.efi Image partition label not found LoadImageFromPartitionUsingGuid Failed: 14 EFI_QseecomStartApp: Load Failed: Status(0x800000000000000E) MinidumpTALib:LoadImageFromPartition(mdcompress) failed: 0xNot Found MinidumpTADxe: Minidump TA loading failed. Error: Image at 0009D2A6000 start failed: Not found - 0x09D294000 [ 2037] UsbMsdDxe.efi - 0x09D287000 [ 2038] UsbDeviceDxe.efi - 0x09D2A7000 [ 2038] UsbInitDxe.efi - 0x09D27E000 [ 2039] ParserDxe.efi - 0x09D277000 [ 2040] SerialPortDxe.efi BDS Entry [ 2040] Disp init wait [ 2040] ----------------------------- Platform Init [ 2057] BDS Boot Cycle : 1 Run Cycle : 1 UEFI Ver : 6.0.231205.BOOT. Platform : IOT Subtype : 1 Boot Device : UFS Chip Name : Chip Ver : 1.0 Chip Serial Number : <0xXxxxxxx> Boot Core : 0 AppsProcClkMHz ----------------------------- - 0x09D21C000 [ 2114] QcomChargerApp.efi Protective MBR validation might be needed. Protective MBR validation might be needed. ERROR: A bit not set ! AppsProcClkMHz is zero Firmware update failed - Status: Unsupported Firmware provisioning failed Platform Init End : 2282 ----------------------------- [QcomBds] BootOrder not found Protective MBR validation might be needed. Protective MBR validation might be needed. [QcomBds] Enumerating non-removable boot options [QcomBds] Adding new boot/driver option Boot0000, Description: Non-removable Media Booting option 0:(Boot0000) "Non-removable Media" UEFI Total : 886 ms POST Time [ 2454] OS Loader - 0x1C22E0000 [ 2456] - 0x1D1F80000 [ 2655] - 0x1FDD00000 [ 2688] EFI stub: Booting Linux Kernel... EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... Start EBS [ 2717] MDPUpdateDynamicClocks: Clock management not supported! MDPUpdateCoreClockAndBandwidth: MDPUpdateDynamicClocks failed! MDPLib: MDPUpdateCoreClockAndBandwidth failed! MDPUpdateDynamicClocks: Clock management not supported! MDPUpdateCoreClockAndBandwidth: MDPUpdateDynamicClocks failed! MDPLib: MDPUpdateCoreClockAndBandwidth failed! MDPLib: SW Render enabled, no Clocks disabled need MDPLib: SW Render enabled, no Clocks disabled need MDPLib: SW Render enabled, no Clocks disabled need MDPLib: SW Render enabled, no Clocks disabled need Successfully synced all UEFI tables Sync Duration = 40 ms Warning: Clearing A-bit ! App Log Flush : 315 ms ScmArmV8ExitBootServicesHandler, Status = 0x0. Exit EBS ``[ 3086] UEFI End`` Copy to clipboard Last Published: May 11, 2026 [Previous Topic PBL/XBL log](https://docs.qualcomm.com/bundle/publicresource/80-80022-4/topics/bootloader-logs.md) [Next Topic Linux log](https://docs.qualcomm.com/bundle/publicresource/80-80022-4/topics/hlos-logging.md)