Client hangs at EFI stub:

[sgilbe]

@rodluz Is it possible to try and get a new kernel with version 6.6.0 I have been told it could fix this issue.

[sgilbe]

@george1421 I have been able to get a debug BIOS for my system and was able to capture from a serial port more detail. I know it has been a while since this was updated but was thinking this could give more light to the issue. This is not the full file it is just from the select boot device (USB Drive) to the hang.

Debug out:
Disabling CR4.SMXE…
-> Register 0x11: Pause Resume Complete = 0x01 0x01 0x00
CheckpointSend 0x08? Yes
-> Register 0x11: Pause Resume Complete = 0x01 0x01 0x01
CheckpointSend 0x09? Yes
-> Ready To Boot: Pause Resume Complete = 0x01 0x01 0x01
[HECI Transport-1 DXE] Send pkt: 80040007
00: FF 0C 00 00
[HECI Transport-1 DXE] Got pkt: 80080007
00: FF 8C 00 00 00 00 00 00
IioSecureOnOnReadyToBoot…
IOAT_INIT_READY_TO_BOOT_START
IOAT_INIT_READY_TO_BOOT_END
IOAT_INIT_READY_TO_BOOT_START
IOAT_INIT_READY_TO_BOOT_END
[TDX_LATE] TdxDxeCallbackOnReadyToBoot BEGIN
[TDX_LATE-GET_FROM_ESP] GetTdxSeamldrFromEsp BEGIN
[LoadFileFromEsp] BEGIN
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Error (Not Found)
[TDX_LATE-GET_FROM_ESP] GetTdxSeamldrFromEsp END (Not Found)
Error: Unable find TdxSeamldr in ESP
[TDX_LATE-GET_FROM_FV] GetTdxSeamldrFromFv BEGIN
[TDX_LATE-GET_FROM_FV] GetTdxSeamldrFromFv END (Success)
TdxSeamldrAddress (FV): 0x63392018
TdxSeamldrSize (FV): 0x35000
[TDX_LATE-GET_FROM_ESP] GetTdxSeamFromEsp BEGIN
[LoadFileFromEsp] BEGIN
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Error (Not Found)
[TDX_LATE-GET_FROM_ESP] GetTdxSeamFromEsp END (Not Found)
Error: Unable find TdxSeam in ESP, aborting!
Unable to find TDX binaries in ESP, falling back to FV!
[TDX_LATE-GET_FROM_FV] GetTdxSeamFromFv BEGIN
[TDX_LATE-GET_FROM_FV] GetTdxSeamFromFv END (Success)
TdxSeamAddress (FV): 0x63344018
TdxSeamSize (FV): 0x26000
[TDX_LATE-GET_FROM_FV] GetTdxSeamSigFromFv BEGIN
[TDX_LATE-GET_FROM_FV] GetTdxSeamSigFromFv END (Success)
TdxSeamSigAddress (FV): 0x64E12018
TdxSeamSigSize (FV): 0x800
[TDX_LATE-HANDLE_SEAMLDR] HandleTdxSeamldr BEGIN
[TDX_LATE-HANDLE_SEAMLDR] ValidateSeamldrBinary BEGIN
[TDX_LATE-HANDLE_SEAMLDR] ValidateSeamldrBinary END (Success)
[TDX_LATE-HANDLE_SEAMLDR] ProgramTdxSeamldrSeSvn BEGIN
Extracted SE_SVN = 0x04 from ACM_HEADER!
Extracted SE_SVN = 0x00 from NVRAM!
Seamldr SE_SVN = 0x04 selected from ACM_HEADER!
[TDX_LATE-HANDLE_SEAMLDR] ProgramTdxSeamldrSeSvn END (Success)
[TDX_LATE-HANDLE_SEAMLDR] LoadTdxSeamldr BEGIN
AsmLaunchTdxSeamldr BEGIN (0x6330F000)
AsmLaunchTdxSeamldr END (0x0)
[TDX_LATE-HANDLE_SEAMLDR] LoadTdxSeamldr END (Success)
[TDX_LATE-HANDLE_SEAMLDR] HandleTdxSeamldr END (Success)
[TDX_LATE-HANDLE_SEAM] HandleTdxSeam BEGIN
[TDX_LATE-VMX] BaseFruUcode4v0_SetCrsForVmx BEGIN
[TDX_LATE-VMX] BaseFruUcode4v0_SetCrsForVmx END (Success)
[TDX_LATE-VMX] VmxOnAndSeamcallThenVmxOffOnAllLps BEGIN
[TDX_LATE-VMX] VmxOnAndSeamcallThenVmxOffOnAllLps END (Success)
[TDX_LATE-HANDLE_SEAM] HandleTdxSeam END (Success)
[TDX_LATE] TdxDxeCallbackOnReadyToBoot END
SmmInstallProtocolInterface: 6E057ECF-FA99-4F39-95BC-59F9921D17E4 0
[SmbiosIFWI] Get Ifwi Version failed.
[HECI Transport-1 DXE] Send pkt: 80040007
00: FF 02 00 00
[HECI Transport-1 DXE] Got pkt: 80140007
00: FF 82 00 00 01 00 06 18 - 30 00 02 00 01 00 06 18
10: 30 00 02 00
TPM Location configured (expected values: dTPM = 0x5 = 0x5
Value at TPM Base Address (0xFED40000) = 0xA1
HierarchyChangeAuth: Response Code error! 0x000009A2
PROGRESS CODE: V03051001 I0
PROGRESS CODE: V03058000 I0
PROGRESS CODE: V03058001 I0
GNU GRUB version 2.06

/----------------------------------------------------------------------------\||||||||||||||||||||||||||----------------------------------------------------------------------------/ Use the ^ and v keys to select which entry is highlighted.

  Press enter to boot the selected OS, `e' to edit the commands       

  before booting or `c' for a command-line.                            *1. FOG Image Deploy/Capture                                                 2. Perform Full Host Registration and Inventory                             3. Quick Registration and Inventory                                         4. Client System Information (Compatibility)                                5. Run Memtest86+                                                           6. FOG Debug Kernel                                                         7. FOG iPXE Jumpstart BIOS                                                  8. FOG iPXE Jumpstart EFI                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              1. FOG Image Deploy/Capture                                                *2. Perform Full Host Registration and Inventory                             2. Perform Full Host Registration and Inventory                            *3. Quick Registration and Inventory                                         3. Quick Registration and Inventory                                        *4. Client System Information (Compatibility)                                4. Client System Information (Compatibility)                               *5. Run Memtest86+                                                           5. Run Memtest86+                                                          *6. FOG Debug Kernel                                                        loading the kernel

loading the virtual hard drive

booting kernel…

IioSecureOnExitBootServices…
SmmInstallProtocolInterface: 296EB418-C4C8-4E05-AB59-39E8AF56F00A 0
EnablePatrolScrubatEndofPostCallback Exit
PROGRESS CODE: V03101019 I0

[george1421]

@sgilbe I’m not seeing anything that jumps out at me as being wrong. It surely seems to fail at starting the kernel.

Are you sure you don’t have secure boot enabled on this system?

[sgilbe]

@george1421 Yes secure boot is disabled. Here is a picture of the BIOS setting.

[SaturTP]

I have the same problem on a HP Z8 G5 dual Xeon silver 4410Y some kernels show just the first line, others both

[sgilbe]

@SaturTP I am glad I am not the only one having this issue. Hopefully we can figure out what is causing the issue and get a fix implemented. Currently we are imaging our systems with this issue by hand which is taking a lot more time. I have it on a Quanta and a SMC server as well.

[rodluz]

@sgilbe Hi, sorry for the delay.
I have 3 new kernels to try. I hope one of these works for you https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n?usp=drive_link

If any one of these works, please let me know which one so I can document it.

[Tom Elliott]

@sgilbe Just a thought here, but is there a possible firmware update needed for these devices too?

I don’t think updating the kernels is going to be a bad thing but also ensuring the firmware is updated to the latest for efi stub integration seems the next potentially most logical step?

[SaturTP]

@rodluz @sgilbe Hi, I just found a workarround.

Disabling Virtualization, VTx and VTd makes it boot with every kernel at least in my case.

[sgilbe]

@Tom-Elliott I have updated all systems to the latest firmware versions. I will go and check to make sure again that I am on the latest versions of firmware.

[sgilbe]

@SaturTP I will try disabling virtualization however we do need that to be enabled on our servers. But if this works then at least it is pointing to the possible root of the issue.

[rodluz]

@SaturTP That’s an interesting find, I’ll check why this would be the problem.
@sgilbe If disabling virtualization makes it work for you too, I’ll add one more kernel to the drive share for you to try.

[sgilbe]

@SaturTP I have disabled Virtualization and VTd but unable to find VTx. So far with these two items it is still failing. Where did you find VTx. Just a generalized location will work hopefully.

[sgilbe]

@rodluz I have tried all 3 kernels the dist1 has the same issue. dist2 and 3 show the following message.

Then they go back to the main menu.

[sgilbe]

@rodluz Are you able to try enabling virtualization in the kernel to see if it fixes it for SaturTP maybe it will help me my issue as well.

[rodluz]

@sgilbe I uploaded two more kernels with virtualization enabled (dist_virt_1 & dist_virt_2). Let me know if this works for you.
https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n

[sgilbe]

@rodluz These both give me the same error after loading the kernel. Error: kernel doesn’t support EFI handover. This is the same error I was getting with dist 2 and 3. dist 1 did not give this error.

[rodluz]

@sgilbe Okay, I did some changes and reuploaded dist_virt_1 & dist_virt_2. Can you try them again?

[sgilbe]

@rodluz thank you for your current help on this. I have tried both the 2 new images you have provided and they are both failing back at the booting kernel that I see when I try to boot the original kernels off the USB drive. Would it be helpful for you to be able to remotely access the system and login to it?

[jfernandz]

@SaturTP said in Client hangs at EFI stub::

@rodluz @sgilbe Hi, I just found a workarround.

Disabling Virtualization, VTx and VTd makes it boot with every kernel at least in my case.

I can confirm just disabling VT the kernel boots , thank you @SaturTP