Date   

Re: Bonding support for PXE Boot

Michael Brown
 

On 06/02/2021 04:36, UdayS via groups.io wrote:
How can I support Bonding of ports and use new Virtual interface for PXE Boot in Hot-Standby mode in UEFI.
Is their any limitation on why it is NOT already supported yet.
Not sure if this would work in your boot scenario, but iPXE already allows you to PXE boot from a switch port that requires the use of port bonding via LACP (also known as IEEE 802.3ad or 802.1AX).

Network booting requires only a few seconds of data transfer that can trivially be retried if the link happens to be disrupted. iPXE therefore includes only a very simple LACP responder: any time it receives an LACP packet it will send a reply with some sane default values. For switch ports that have been configured to use port bonding with LACP, this is sufficient to convince the switch that the port is active.

I don't see any reference to port bonding within the EDK2 source code, so it doesn't look as though it's supported yet by standard UEFI PXE boot, sorry.

Hope that helps,

Michael


Re: How to execute Tpm2CommandClear with Physical Presence?

joseph@...
 

Using Tpm2DeviceLibTcg2 instead of Tpm2DeviceLibDTpm changed the error content.

Tpm2ClearControl - Device Error
ClearControl: Response Code error! 0x00000185
The contents of the error are the same even as execute the below code.
How can I use Platform Authentication?
Tcg2PhysicalPresenceLibSubmitRequestToPreOSFunction(TCG2_PHYSICAL_PRESENCE_CLEAR, 0);
Tcg2PhysicalPresenceLibProcessRequest(NULL);


Re: How to link DXE_DRIVER from UEFI_APPLICATION?

joseph@...
 

Oh, this was my mistake.
The above error was because the Tpm2DeviceLib and Tpm2DeviceLibTcg2 libraries were linked both.

Tpm2DeviceLib|SecurityPkg/Library/Tpm2DeviceLibDTpm/Tpm2DeviceLibDTpm.inf
Tpm2DeviceLibTcg2|SecurityPkg/Library/Tpm2DeviceLibTcg2/Tpm2DeviceLibTcg2.inf
This discussion seems to be resolved.
I need to go to Bugzilla.

Thanks.


Re: Compile EDK2 to set boot order to PXE

Pete Batard
 

On 2021.02.06 16:01, Werner Buck wrote:
It is exactly as Micheal Brown put it. Thank you for all your thoughts into this!

> 1. UEFI firmware defaults to attempting a network boot if no SD card is
present.  This would allow the UEFI firmware to load iPXE via TFTP.
Actually this is what is surprising to me. When RPI4 UEFI is running it tries to boot `efi/boot/bootaa64.efi` as a first option but as the uefi is running from network boot is unable to find it. I would expect the firmware to then choose network boot but the pi actually does a reboot loop.
I believe the way Raspberry Pi defaults to network boot is actually by updating the boot options and issuing a reboot, per: https://github.com/tianocore/edk2-platforms/commit/8dd78ea11a38d2d7e8031c4783e9f2ca5569956b

In other words, we currently rely on hitting PlatformBootManagerUnableToBoot() once, so that we update the boot options, and then reboot the system into an environment that now has network boot as default.

You can validate this by simply extracting a newly built UEFI firmware (such as the one from the official archives) on USB/SD and powering up. You'll see that it takes one reboot, before it starts to look for network files.

But of course, that only works if you can save variables... which you can't do in this scenario. If you are downloading the same "pristine" UEFI firmware over and over, you will indeed hit a boot loop.

CCing Samer, who might have looked at alternatives to enable network boot by default, and could have some ideas of how we may achieve this, in a scenario where we can't save boot variables...

Regards,

/Pete

Mind that this is all without an SD card present currently. Should I raise a bug for this at the RPI4 platform side?
I am actually doing triple network boot here. And have actually had 0 reliability problems with network booting at least on the RPI4 with DHCP ISC server with the below config and having dnsmasq serve an tftp server.
Just for transparency this is what im running in an isc dhcp server:
```
# network boot coming in
if substring (option vendor-class-identifier,0,9) = "PXEClient" {
        option tftp-server-name "10.10.10.1";
        # raspberry pi defaults to loading bootcode.bin from tftp and i have the rpi4 uefi firmware just extracted on the tftproot.
        # when booted using uefi and starting network boot again architecture is 00:0b (uefi arm64) and we download iPXE
        if option arch = 00:0b {
           log(info, "This is UEFI ARM boot (raspberry pi), booting ipxe..");
           #specially compiled ipxe with 8gb
           filename "ipxe-pi.efi";
        }
}
# Detecting ipxe https flag so we point filename to the boot.ipxe filename.
if exists ipxe.https {
  log (info, "ipxe enabled");
  # matchbox server
  filename "http://10.10.10.1:8085/boot.ipxe <http://10.10.10.1:8085/boot.ipxe>";
}
```
Packing iPXE in some way and tricking UEFI with the PCD file GUID is what im going to try this weekend!
Thanks all I will keep you posted.
Werner Buck
Op do 4 feb. 2021 om 13:54 schreef Laszlo Ersek <lersek@redhat.com <mailto:lersek@redhat.com>>:
On 02/04/21 13:35, Michael Brown wrote:
> On 04/02/2021 08:56, Laszlo Ersek wrote:
>> I've attempted to wrap my brain around the initial report in this
>> thread, and honestly I'm lost. My standard answer would be "BDS
behavior
>> is platform policy, so look into whatever PlatformBootManagerLib
>> instance is used by the RPi firmware" (and I understand that Ard's
>> response is somehow consistent with this). But honestly I can't
figure
>> out whether the problem is related to the part of the RPi
firmware that
>> runs *before* TianoCore. What exactly is PXE-booted before what
else?...
>> I think we'd need a much more detailed issue report here.
>
> My best guess (based on having tried to do something similar
before) is:
>
> - Pi has no local storage.
>
> - Pi uses its builtin network boot (running on the VC4 GPU, not
the CPU)
> to download bootcode.bin, config.txt, and an appropriate
start*.elf via
> TFTP.
>
> - The downloaded config.txt includes "armstub=RPI_EFI.fd".  The
VC4 GPU
> (now executing start*.elf, as far as I am aware) downloads RPI_EFI.fd
> and boots the ARM CPU into this.
>
> - At this point, we have the CPU running the RPi UEFI firmware.
>
> There is no non-volatile storage available
O_o
Thank you for the explanation. Not that I can help Werner in any way,
but now I understand the issue at least.
Thanks,
Laszlo

> and so no way to use EFI
> variables to control the boot order.  The boot device will be
whatever
> is the *compile-time* default for RPI_EFI.fd.
>
> The intention is that the UEFI firmware should then attempt a network
> boot.  This could be done in at least three ways:
>
> 1. UEFI firmware defaults to attempting a network boot if no SD
card is
> present.  This would allow the UEFI firmware to load iPXE via TFTP.
>
> 2. iPXE as a driver (specifically bin-arm64-efi/rpi.efidrv) is
embedded
> within the RPI_EFI.fd image, and UEFI firmware defaults to
attempting a
> network boot if no SD card is present.
>
> 3. iPXE as an application (specifically bin-arm64-efi/rpi.efi) is
> embedded within the RPI_EFI.fd image, and UEFI firmware somehow
defaults
> to running this application (e.g. via the PCD file GUID trick
suggested
> by Ard).
>
> All three of these options would result in the RPi running UEFI
iPXE as
> requested.
>
> Werner: please correct me if I have misunderstood what you are
trying to
> do.
>
> Thanks,
>
> Michael
>


Potentially missing CloseProtocol() call

Satoshi Tanda
 

There are a number of places that do not call CloseProtocol() while it
appears to be required, in EDK2. Can someone confirm if (some of) those are
indeed errors, or there are actually cases where skipping CloseProtocol()
after OpenProtocol() is appropriate?

Here are the places I would expect a CloseProtocol() call but apparently
missing it.

MdeModulePkg/Universal/DebugSupportDxe/DebugSupport.c
- InitializeDebugSupportDriver().

ShellPkg/Library/UefiShellDriver1CommandsLib/Dh.c
- GetDriverName() / GetDriverImageName()

ShellPkg/Library/UefiHandleParsingLib/UefiHandleParsingLib.c
- *ProtocolDumpInformation(). DevicePathProtocolDumpInformationEx() does
call it. So lack of call seems like an error to me.

ShellPkg/Library/UefiShellDriver1CommandsLib/DevTree.c
- DoDevTreeForHandle()

I am new to UEFI and trying to learn basics like how to use OpenProtocol().
I have not observed or encountered any concrete issue.

Best,
Satoshi


Re: Compile EDK2 to set boot order to PXE

wernerbuck@...
 

It is exactly as Micheal Brown put it. Thank you for all your thoughts into
this!

1. UEFI firmware defaults to attempting a network boot if no SD card is
present. This would allow the UEFI firmware to load iPXE via TFTP.
Actually this is what is surprising to me. When RPI4 UEFI is running it
tries to boot `efi/boot/bootaa64.efi` as a first option but as the uefi is
running from network boot is unable to find it. I would expect the firmware
to then choose network boot but the pi actually does a reboot loop.
Mind that this is all without an SD card present currently. Should I raise
a bug for this at the RPI4 platform side?

I am actually doing triple network boot here. And have actually had 0
reliability problems with network booting at least on the RPI4 with DHCP
ISC server with the below config and having dnsmasq serve an tftp server.
Just for transparency this is what im running in an isc dhcp server:

```
# network boot coming in
if substring (option vendor-class-identifier,0,9) = "PXEClient" {
option tftp-server-name "10.10.10.1";
# raspberry pi defaults to loading bootcode.bin from tftp and i
have the rpi4 uefi firmware just extracted on the tftproot.
# when booted using uefi and starting network boot again
architecture is 00:0b (uefi arm64) and we download iPXE
if option arch = 00:0b {
log(info, "This is UEFI ARM boot (raspberry pi), booting
ipxe..");
#specially compiled ipxe with 8gb
filename "ipxe-pi.efi";
}
}
# Detecting ipxe https flag so we point filename to the boot.ipxe filename.
if exists ipxe.https {
log (info, "ipxe enabled");
# matchbox server
filename "http://10.10.10.1:8085/boot.ipxe";
}
```

Packing iPXE in some way and tricking UEFI with the PCD file GUID is what
im going to try this weekend!

Thanks all I will keep you posted.

Werner Buck


Op do 4 feb. 2021 om 13:54 schreef Laszlo Ersek <lersek@redhat.com>:

On 02/04/21 13:35, Michael Brown wrote:
On 04/02/2021 08:56, Laszlo Ersek wrote:
I've attempted to wrap my brain around the initial report in this
thread, and honestly I'm lost. My standard answer would be "BDS behavior
is platform policy, so look into whatever PlatformBootManagerLib
instance is used by the RPi firmware" (and I understand that Ard's
response is somehow consistent with this). But honestly I can't figure
out whether the problem is related to the part of the RPi firmware that
runs *before* TianoCore. What exactly is PXE-booted before what else?...
I think we'd need a much more detailed issue report here.
My best guess (based on having tried to do something similar before) is:

- Pi has no local storage.

- Pi uses its builtin network boot (running on the VC4 GPU, not the CPU)
to download bootcode.bin, config.txt, and an appropriate start*.elf via
TFTP.

- The downloaded config.txt includes "armstub=RPI_EFI.fd". The VC4 GPU
(now executing start*.elf, as far as I am aware) downloads RPI_EFI.fd
and boots the ARM CPU into this.

- At this point, we have the CPU running the RPi UEFI firmware.

There is no non-volatile storage available
O_o

Thank you for the explanation. Not that I can help Werner in any way,
but now I understand the issue at least.

Thanks,
Laszlo

and so no way to use EFI
variables to control the boot order. The boot device will be whatever
is the *compile-time* default for RPI_EFI.fd.

The intention is that the UEFI firmware should then attempt a network
boot. This could be done in at least three ways:

1. UEFI firmware defaults to attempting a network boot if no SD card is
present. This would allow the UEFI firmware to load iPXE via TFTP.

2. iPXE as a driver (specifically bin-arm64-efi/rpi.efidrv) is embedded
within the RPI_EFI.fd image, and UEFI firmware defaults to attempting a
network boot if no SD card is present.

3. iPXE as an application (specifically bin-arm64-efi/rpi.efi) is
embedded within the RPI_EFI.fd image, and UEFI firmware somehow defaults
to running this application (e.g. via the PCD file GUID trick suggested
by Ard).

All three of these options would result in the RPi running UEFI iPXE as
requested.

Werner: please correct me if I have misunderstood what you are trying to
do.

Thanks,

Michael


How to execute Tpm2CommandClear with Physical Presence?

joseph@...
 

Hi,

I want to Clear TPM.

So, I tried to execute Tpm2CommandClear, not work.
Tpm2ClearControl ...
Tpm2ClearControl - Not Found
How to clear TPM2 with Physical Presence?

Kind regards,
Joseph


Re: How to link DXE_DRIVER from UEFI_APPLICATION?

joseph@...
 

Hi Laszlo,

Thank you. But the problem is still not solved.

.../edk2/MyPkg/MyPkg.dsc(...): error 1001: Module type [UEFI_APPLICATION] is not supported by
library instance [.../edk2/SecurityPkg/Library/Tcg2PpVendorLibNull/Tcg2PpVendorLibNull.inf]
consumed by [.../edk2/MyPkg/MyApp/MyApp.inf]
After modifying several more steps through the method you suggested, the build was completed.
https://github.com/jc-lab/temp-edk2-tpm2-problem/commit/d9afc8f562d1bda190b27ac8db67df3b0a5bb24a
But I get the error like below.

/usr/bin/ld: Tpm2DeviceLibTcg2.obj (symbol from plugin): in function `mTcg2Protocol':
(.text+0x0): multiple definition of `Tpm2SubmitCommand'; Tpm2DeviceLibDTpm.obj (symbol from plugin):(.text+0x0): first defined here
/usr/bin/ld: Tpm2DeviceLibTcg2.obj (symbol from plugin): in function `mTcg2Protocol':
(.text+0x0): multiple definition of `Tpm2RequestUseTpm'; Tpm2DeviceLibDTpm.obj (symbol from plugin):(.text+0x0): first defined here
/usr/bin/ld: Tpm2DeviceLibTcg2.obj (symbol from plugin): in function `mTcg2Protocol':
(.text+0x0): multiple definition of `Tpm2RegisterTpm2DeviceLib'; Tpm2DeviceLibDTpm.obj (symbol from plugin):(.text+0x0): first defined here
collect2: error: ld returned 1 exit status
make: *** [GNUmakefile:375: ...MyApp.dll] Error 1
Can you help me a little more?
I will also create a Bugzilla ticket soon.

Kind regards,
Joseph


Bonding support for PXE Boot

UdayS
 

Hello Experts,
How can I support Bonding of ports and use new Virtual interface for PXE Boot in Hot-Standby mode in UEFI.
Is their any limitation on why it is NOT already supported yet.

-US


Re: [EXTERNAL] Re: [edk2-discuss] How to link DXE_DRIVER from UEFI_APPLICATION?

Bret Barkelew
 

Yeah, DxeTcg2PhysicalPresence could use some TLC. It’s a weird catch-all of stuff which should be refactored.
I’ve had it on my backlog forever.

- Bret

From: Laszlo Ersek via groups.io<mailto:lersek=redhat.com@groups.io>
Sent: Friday, February 5, 2021 7:47 AM
To: joseph@zeronsoftn.com<mailto:joseph@zeronsoftn.com>; discuss@edk2.groups.io<mailto:discuss@edk2.groups.io>
Subject: [EXTERNAL] Re: [edk2-discuss] How to link DXE_DRIVER from UEFI_APPLICATION?

On 02/05/21 15:44, joseph via [] wrote:
Hi, Laszlo

Thank you for reply.

My app does not use UefiDriverEntryPoint.
UefiDriverEntryPoint exists in DxeTcg2PhysicalPresenceLib.inf.
Ouch. That's a bug in "DxeTcg2PhysicalPresenceLib.inf", no doubt.

Let's see if there are some other library INF files that have a similar issue:

$ git grep -l -w UefiDriverEntryPoint -- '*inf' \
| xargs grep -l -w LIBRARY_CLASS

MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib.inf
MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf
SecurityPkg/Library/DxeTcg2PhysicalPresenceLib/DxeTcg2PhysicalPresenceLib.inf
SecurityPkg/Library/DxeTcgPhysicalPresenceLib/DxeTcgPhysicalPresenceLib.inf

OK, so the bugged library INF files are:
- CustomizedDisplayLib.inf
- DxeTcg2PhysicalPresenceLib.inf
- DxeTcgPhysicalPresenceLib.inf

Can you please file a bugzilla ticket at <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.tianocore.org%2F&;data=04%7C01%7Cbret.barkelew%40microsoft.com%7Ca5ed4a8cc1d74674a28708d8c9ed6450%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637481368714208086%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=cUIKRsSv9HUywTgoybjzT%2FnavUVC4JLdCleHnpxjtg4%3D&amp;reserved=0>, about this? Those library instances should not depend on the UefiDriverEntryPoint class.


If forcibly delete UefiDriverEntryPoint from DxeTcg2PhysicalPresenceLib.inf, Another error occurs.
Instance of library class [Tcg2PpVendorLib] is not found
Wait, that's a different case.

When you delete UefiDriverEntryPoint from DxeTcg2PhysicalPresenceLib.inf, you actually fix a bug. And therefore the build process advances a bit further, before it runs into *another* problem.

This particular (new) problem is that your platform DSC file does not resolve the Tcg2PpVendorLib class to a library instance. DxeTcg2PhysicalPresenceLib depends on Tcg2PpVendorLib, but the build process doesn't know what instance of Tcg2PpVendorLib to use. Edk2 offers a Null instance of this library:

SecurityPkg/Library/Tcg2PpVendorLibNull/Tcg2PpVendorLibNull.inf

So in your DSC file, you could use:

[LibraryClasses]
Tcg2PpVendorLib|SecurityPkg/Library/Tcg2PpVendorLibNull/Tcg2PpVendorLibNull.inf

Hope this helps,
Laszlo

Adding the Tcg2PpVendorLib again gives me the "error 1001" error.

========== MyApp.inf =========
[LibraryClasses]
UefiApplicationEntryPoint
UefiLib
PcdLib
OpensslLib
Tpm2DeviceLibTcg2
Tcg2PhysicalPresenceLib

========== DxeTcg2PhysicalPresenceLib.inf =========
[LibraryClasses]
MemoryAllocationLib
UefiLib
UefiBootServicesTableLib
UefiDriverEntryPoint
UefiRuntimeServicesTableLib
BaseMemoryLib
DebugLib
PrintLib
HiiLib
HobLib
Tpm2CommandLib
Tcg2PpVendorLib


Re: How to link DXE_DRIVER from UEFI_APPLICATION?

Laszlo Ersek
 

On 02/05/21 15:44, joseph via [] wrote:
Hi, Laszlo

Thank you for reply.

My app does not use UefiDriverEntryPoint.
UefiDriverEntryPoint exists in DxeTcg2PhysicalPresenceLib.inf.
Ouch. That's a bug in "DxeTcg2PhysicalPresenceLib.inf", no doubt.

Let's see if there are some other library INF files that have a similar issue:

$ git grep -l -w UefiDriverEntryPoint -- '*inf' \
| xargs grep -l -w LIBRARY_CLASS

MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib.inf
MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf
SecurityPkg/Library/DxeTcg2PhysicalPresenceLib/DxeTcg2PhysicalPresenceLib.inf
SecurityPkg/Library/DxeTcgPhysicalPresenceLib/DxeTcgPhysicalPresenceLib.inf

OK, so the bugged library INF files are:
- CustomizedDisplayLib.inf
- DxeTcg2PhysicalPresenceLib.inf
- DxeTcgPhysicalPresenceLib.inf

Can you please file a bugzilla ticket at <https://bugzilla.tianocore.org/>, about this? Those library instances should not depend on the UefiDriverEntryPoint class.


If forcibly delete UefiDriverEntryPoint from DxeTcg2PhysicalPresenceLib.inf, Another error occurs.
Instance of library class [Tcg2PpVendorLib] is not found
Wait, that's a different case.

When you delete UefiDriverEntryPoint from DxeTcg2PhysicalPresenceLib.inf, you actually fix a bug. And therefore the build process advances a bit further, before it runs into *another* problem.

This particular (new) problem is that your platform DSC file does not resolve the Tcg2PpVendorLib class to a library instance. DxeTcg2PhysicalPresenceLib depends on Tcg2PpVendorLib, but the build process doesn't know what instance of Tcg2PpVendorLib to use. Edk2 offers a Null instance of this library:

SecurityPkg/Library/Tcg2PpVendorLibNull/Tcg2PpVendorLibNull.inf

So in your DSC file, you could use:

[LibraryClasses]
Tcg2PpVendorLib|SecurityPkg/Library/Tcg2PpVendorLibNull/Tcg2PpVendorLibNull.inf

Hope this helps,
Laszlo

Adding the Tcg2PpVendorLib again gives me the "error 1001" error.

========== MyApp.inf =========
[LibraryClasses]
UefiApplicationEntryPoint
UefiLib
PcdLib
OpensslLib
Tpm2DeviceLibTcg2
Tcg2PhysicalPresenceLib

========== DxeTcg2PhysicalPresenceLib.inf =========
[LibraryClasses]
MemoryAllocationLib
UefiLib
UefiBootServicesTableLib
UefiDriverEntryPoint
UefiRuntimeServicesTableLib
BaseMemoryLib
DebugLib
PrintLib
HiiLib
HobLib
Tpm2CommandLib
Tcg2PpVendorLib


Re: How to link DXE_DRIVER from UEFI_APPLICATION?

joseph@...
 

Hi, Laszlo

Thank you for reply.

My app does not use UefiDriverEntryPoint.
UefiDriverEntryPoint exists in DxeTcg2PhysicalPresenceLib.inf.
If forcibly delete UefiDriverEntryPoint from DxeTcg2PhysicalPresenceLib.inf, Another error occurs.
Instance of library class [Tcg2PpVendorLib] is not found
Adding the Tcg2PpVendorLib again gives me the "error 1001" error.

========== MyApp.inf =========
[LibraryClasses]
UefiApplicationEntryPoint
UefiLib
PcdLib
OpensslLib
Tpm2DeviceLibTcg2
Tcg2PhysicalPresenceLib

========== DxeTcg2PhysicalPresenceLib.inf =========
[LibraryClasses]
MemoryAllocationLib
UefiLib
UefiBootServicesTableLib
UefiDriverEntryPoint
UefiRuntimeServicesTableLib
BaseMemoryLib
DebugLib
PrintLib
HiiLib
HobLib
Tpm2CommandLib
Tcg2PpVendorLib


Re: How to link DXE_DRIVER from UEFI_APPLICATION?

Laszlo Ersek
 

On 02/05/21 07:59, joseph via groups.io wrote:
Hi,

I want to include Tcg2PhysicalPresenceLib in my UEFI Application.

Tcg2PhysicalPresenceLib is located in SecurityPkg/Library/Tpm2DeviceLibTcg2/Tpm2DeviceLibTcg2.inf in EDK2.

========================================
This is what I tried:

Package dsc:
[LibraryClasses.common]
Tpm2DeviceLibTcg2|SecurityPkg/Library/Tpm2DeviceLibTcg2/Tpm2DeviceLibTcg2.inf

Application inf:
[LibraryClasses]
Tcg2PhysicalPresenceLib
========================================

If you do the above, you will get this error.

.../edk2/MyPkg/MyPkg.dsc(...): error 1001: Module type [UEFI_APPLICATION] is not supported by library instance [.../edk2/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf]
consumed by [.../edk2/MyPkg/MyApp/MyApp.inf]

How do I use Tcg2PhysicalPresenceLib in Application?
"SecurityPkg/Library/Tpm2DeviceLibTcg2/Tpm2DeviceLibTcg2.inf" already
permits UEFI_APPLICATION, so that's not the problem.

The issue is that you're trying to link UefiDriverEntryPoint into your
application -- that's wrong. UEFI_APPLICATION modules have different
entry points / depend on different entry point lib classes, namely one
of the following:

- "UefiApplicationEntryPoint" if the application is stand-alone (for
example, bootable as a UEFI boot option)

- "ShellCEntryLib" if the application is a shell application (= it can,
and needs to, be started from the UEFI shell only)

- "LibC" if the application consumes the edk2-libc project for a
standard C library implementation, and starts with a main() function.

Laszlo


Re: UEFI Payload Issue

sent888@...
 

On Thu, Feb 4, 2021 at 09:40 PM, "Ma, Maurice" <maurice.ma@intel.com> wrote:

Hi,

Thanks for your suggestions.

I tried latest edk2 Uefipayload but it not loading. It showing below error

BS: BS_PAYLOAD_LOAD times (us): entry 569738 run 670788 exit 32811
BS: Entering BS_PAYLOAD_BOOT state.
mp_park_aps done after 0 msecs.
Jumping to boot code at 008055c0(89c63000)
ASSERT [PayloadEntry] /home/edk2/MdePkg/Library/BasePcdLibNull/PcdLib.c(123): ((BOOLEAN)(0==1))



So i went edk2 2017 version and CorebootPayloadPkg. My coreboot version is 4.9. In EDK2 2017 in the log i am getting below error also

[Bds] Entry...
[BdsDxe] Locate Variable Lock protocol - Not Found

UsbSelectConfig: failed to connect driver Not Found, ignored

Is this error related to hung at BdsWait...

The complete log is below..............


BS: Exiting BS_PAYLOAD_LOAD state.
BS: callback (89ce221c) @ src/cpu/x86/mtrr/mtrr.c:891.
BS: callback (89ce1f84) @ src/drivers/intel/fsp2_0/notify.c:82.
BS: callback (89cdf13c) @ src/soc/intel/cannonlake/pmc.c:79.
BS: callback (89cdf094) @ src/soc/intel/cannonlake/finalize.c:107.
Finalizing chipset.
Finalizing SMM.
----------------------------------------
BS: BS_PAYLOAD_LOAD times (us): entry 115414 run 622098 exit 32819
BS: Entering BS_PAYLOAD_BOOT state.
mp_park_aps done after 0 msecs.
Jumping to boot code at 00800820(89c63000)
PROGRESS CODE: V03020003 I0
Loading PEIM at 0x00000813A40 EntryPoint=0x00000813C80 CbSupportPeim.efi
PROGRESS CODE: V03020002 I0
0. 0000000000000000 - 0000000000000FFF [10]
1. 0000000000001000 - 000000000009FFFF [01]
2. 00000000000A0000 - 00000000000FFFFF [02]
3. 0000000000100000 - 0000000089C3CFFF [01]
4. 0000000089C3D000 - 0000000089FFFFFF [10]
5. 000000008A000000 - 000000008F7FFFFF [02]
6. 00000000E0000000 - 00000000EFFFFFFF [02]
7. 00000000FC000000 - 00000000FC000FFF [02]
8. 00000000FE000000 - 00000000FE00FFFF [02]
9. 00000000FED10000 - 00000000FED17FFF [02]
10. 00000000FED80000 - 00000000FED83FFF [02]
11. 00000000FED90000 - 00000000FED91FFF [02]
12. 00000000FEDA0000 - 00000000FEDA1FFF [02]
13. 0000000100000000 - 000000046C7FFFFF [01]
Low memory 0x89C3D000
SystemLowMemTop 0x90000000
PeiMemBase: 0x85C30000.
PeiMemSize: 0x4000000.
PeiInstallPeiMemory MemoryBegin 0x85C30000, MemoryLength 0x4000000
Found one valid fv : 0x3E000000830000.
Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 807A19
The 1th FV start address is 0x00000830000, size is 0x003E0000, handle is 0x830000
Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410
Actual Coreboot header: 89C63000.
Find CbMemTable Id 0x41435049, base 89C3F000, size 0x24000
Find CbMemTable Id 0x534D4254, base 89C3D000, size 0x800
Detected Acpi Table at 0x89C3F000, length 0x24000
Detected Smbios Table at 0x89C3D000, length 0x800
Create system table info guid hob
Find CbMemTable Id 0x41435049, base 89C3F000, size 0x24000
Find Rsdp at 89C3F000
Find Rsdt 0x89C3F030, Xsdt 0x89C3F0E0
PmCtrl Reg 0x1804
PmTimer Reg 0x1808
Reset Reg 0xCF9
Reset Value 0x6
PmEvt Reg 0x1800
PmGpeEn Reg 0x1870
Create acpi board info guid hob
Found coreboot video frame buffer information
physical_address: 0xC0000000
x_resolution: 0x780
y_resolution: 0x438
bits_per_pixel: 0x20
bytes_per_line: 0x1E00
red_mask_size: 0x8
red_mask_pos: 0x10
green_mask_size: 0x8
green_mask_pos: 0x8
blue_mask_size: 0x8
blue_mask_pos: 0x0
reserved_mask_size: 0x18
reserved_mask_pos: 0x18
Create frame buffer info guid hob
PROGRESS CODE: V03020003 I0
Temp Stack : BaseAddress=0x88000 Length=0x8000
Temp Heap : BaseAddress=0x80000 Length=0x8000
Total temporary memory: 65536 bytes.
temporary memory stack ever used: 32768 bytes.
temporary memory heap used: 3832 bytes.
Old Stack size 32768, New stack size 131072
Stack Hob: BaseAddress=0x85C30000 Length=0x20000
Heap Offset = 0x85BD0000 Stack Offset = 0x85BC0000
Loading PEIM at 0x00089C24000 EntryPoint=0x00089C2BED6 PeiCore.efi
Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6
Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE
Loading PEIM at 0x00089C1F000 EntryPoint=0x00089C20258 DxeIpl.efi
PROGRESS CODE: V03020002 I0
PROGRESS CODE: V03020003 I0
Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7
Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731
DXE IPL Entry
Loading PEIM at 0x00089BF6000 EntryPoint=0x00089BF6240 DxeCore.efi
PROGRESS CODE: V03021001 I0
Loading DXE CORE at 0x00089BF6000 EntryPoint=0x00089BF6240
Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6
HandOffToDxeCore() Stack Base: 0x89BD6000, Stack Size: 0x20000
PROGRESS CODE: V03040003 I0
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898CE2C0
Loading driver at 0x000898B2000 EntryPoint=0x000898B2D0F SecurityStubDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898CE898
ProtectUefiImageCommon - 0x898CE2C0
- 0x00000000898B2000 - 0x00000000000075C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 898B8D78
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 898B8D70
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
InstallProtocolInterface: 15853D7C-3DDF-43E0-A1CB-EBF85B8F872C 898B8D50
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898CB2C0
Loading driver at 0x00089896000 EntryPoint=0x00089896240 CpuDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898CB018
ProtectUefiImageCommon - 0x898CB2C0
- 0x0000000089896000 - 0x000000000000DF40
PROGRESS CODE: V03040002 I0
CurrentPagingContext:
MachineType - 0x8664
PageTableBase - 0x89BD4000
Attributes - 0x40000006
InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 898A3940
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
MemoryProtectionCpuArchProtocolNotify:
ProtectUefiImageCommon - 0x89C1B2E8
- 0x0000000089BF6000 - 0x0000000000029000
ProtectUefiImageCommon - 0x898D00C0
- 0x00000000898C2000 - 0x0000000000006740
ProtectUefiImageCommon - 0x898CF840
- 0x0000000089AFF000 - 0x0000000000002D40
ProtectUefiImageCommon - 0x898CEB40
- 0x0000000089AFB000 - 0x0000000000003F00
ProtectUefiImageCommon - 0x898CE2C0
- 0x00000000898B2000 - 0x00000000000075C0
ProtectUefiImageCommon - 0x898CB2C0
- 0x0000000089896000 - 0x000000000000DF40
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
AP Loop Mode is 1
APIC MODE is 1
MpInitLib: Find 12 processors in system.
Detect CPU count: 12
Does not find any HOB stored CPU BIST information!
InstallProtocolInterface: 3FDDA605-A76E-4F46-AD29-12F4531B3D08 898A38E0
PROGRESS CODE: V03040003 I0
Loading driver C8339973-A563-4561-B858-D8476F9DEFC4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898B12C0
Loading driver at 0x000898AD000 EntryPoint=0x000898ADE99 Metronome.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898B1B18
ProtectUefiImageCommon - 0x898B12C0
- 0x00000000898AD000 - 0x0000000000001AC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 26BACCB2-6F42-11D4-BCE7-0080C73C8881 898AE8C0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898B0040
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/tina/edk2-UDK2017/Build/CorebootPayloadPkgX64/DEBUG_GCC5/X64/MdeModulePkg/Core/RuntimeDxe/RuntimeDxe/DEBUG/RuntimeDxe.dll !!!!!!!!
Loading driver at 0x00089AF8000 EntryPoint=0x00089AF8C60 RuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898B1718
ProtectUefiImageCommon - 0x898B0040
- 0x0000000089AF8000 - 0x0000000000002940
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 89AFA300
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver 4B28E4C7-FF36-4E10-93CF-A82159E777C5
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898B03C0
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/tina/edk2-UDK2017/Build/CorebootPayloadPkgX64/DEBUG_GCC5/X64/MdeModulePkg/Universal/ResetSystemRuntimeDxe/ResetSystemRuntimeDxe/DEBUG/ResetSystemRuntimeDxe.dll !!!!!!!!
Loading driver at 0x00089AF5000 EntryPoint=0x00089AF5B53 ResetSystemRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898B0E98
ProtectUefiImageCommon - 0x898B03C0
- 0x0000000089AF5000 - 0x0000000000002400
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 27CFAC88-46CC-11D4-9A38-0090273FC14D 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver 02B01AD5-7E59-43E8-A6D8-238180613A5A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898AF140
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/tina/edk2-UDK2017/Build/CorebootPayloadPkgX64/DEBUG_GCC5/X64/MdeModulePkg/Universal/Variable/EmuRuntimeDxe/EmuVariableRuntimeDxe/DEBUG/EmuVariableRuntimeDxe.dll !!!!!!!!
Loading driver at 0x00089AF0000 EntryPoint=0x00089AF0B00 EmuVariableRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898B0898
ProtectUefiImageCommon - 0x898AF140
- 0x0000000089AF0000 - 0x0000000000004940
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 1E5668E2-8481-11D4-BCF1-0080C73C8881 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
InstallProtocolInterface: 6441F818-6362-4E44-B570-7DBA31DD2453 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898AA040
Loading driver at 0x000898A8000 EntryPoint=0x000898A9364 CpuIo2Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898AF418
ProtectUefiImageCommon - 0x898AA040
- 0x00000000898A8000 - 0x0000000000001E00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F 898A9C40
PROGRESS CODE: V03040003 I0
Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898AA9C0
Loading driver at 0x0008987C000 EntryPoint=0x0008987D7D4 DevicePathDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898AA318
ProtectUefiImageCommon - 0x898AA9C0
- 0x000000008987C000 - 0x000000000000C500
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 89887600
InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C 898875E0
InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E 898875C0
PROGRESS CODE: V03040003 I0
Loading driver 96B5C032-DF4C-4B6E-8232-438DCF448D0E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898ACB40
Loading driver at 0x000898A4000 EntryPoint=0x000898A4CDD NullMemoryTestDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898AA498
ProtectUefiImageCommon - 0x898ACB40
- 0x00000000898A4000 - 0x0000000000001980
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF 898A5740
PROGRESS CODE: V03040003 I0
Loading driver 79CA4208-BBA1-4A9A-8456-E1E66A81484E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898AC1C0
Loading driver at 0x00089894000 EntryPoint=0x000898950A9 Legacy8259.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898AC418
ProtectUefiImageCommon - 0x898AC1C0
- 0x0000000089894000 - 0x0000000000001A00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 38321DBA-4FE0-4E17-8AEC-413055EAEDC1 898957E0
PROGRESS CODE: V03040003 I0
Loading driver 348C4D62-BFBD-4882-9ECE-C80BB1C4783B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898ABC40
Loading driver at 0x0008983C000 EntryPoint=0x0008983F0E5 HiiDatabase.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898ABB98
ProtectUefiImageCommon - 0x898ABC40
- 0x000000008983C000 - 0x000000000001F3C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: E9CA4775-8657-47FC-97E7-7ED65A084324 8985AFC8
InstallProtocolInterface: 0FD96974-23AA-4CDC-B9CB-98D17750322A 8985B040
InstallProtocolInterface: EF9FC172-A1B2-4693-B327-6D32FC416042 8985B068
InstallProtocolInterface: 587E72D7-CC50-4F79-8209-CA291FC1A10F 8985B0C0
InstallProtocolInterface: 0A8BADD5-03B8-4D19-B128-7B8F0EDAA596 8985B0F0
InstallProtocolInterface: 31A6406A-6BDF-4E46-B2A2-EBAA89C40920 8985AFE8
InstallProtocolInterface: 1A1241E6-8F19-41A9-BC0E-E8EF39E06546 8985B010
PROGRESS CODE: V03040003 I0
Loading driver C68DAA4E-7AB5-41E8-A91D-5954421053F3
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898A7C40
Loading driver at 0x0008988E000 EntryPoint=0x0008988EA4C CbSupportDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898AB898
ProtectUefiImageCommon - 0x898A7C40
- 0x000000008988E000 - 0x0000000000002340
PROGRESS CODE: V03040002 I0
Install Acpi Table at 0x89C3F000, length 0x24000
Install Smbios Table at 0x89C3D000, length 0x800
PmCtrlReg at 0x1804
PROGRESS CODE: V03040003 I0
Loading driver F9D88642-0737-49BC-81B5-6889CD57D9EA
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898A7340
Loading driver at 0x00089878000 EntryPoint=0x0008987949D SmbiosDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898A7918
ProtectUefiImageCommon - 0x898A7340
- 0x0000000089878000 - 0x0000000000003780
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 03583FF6-CB36-4940-947E-B9B39F4AFAF7 8987B630
PROGRESS CODE: V03040003 I0
Loading driver D3987D4B-971A-435F-8CAF-4967EB627241
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898A60C0
Loading driver at 0x0008988B000 EntryPoint=0x0008988BF86 SerialDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898A6E18
ProtectUefiImageCommon - 0x898A60C0
- 0x000000008988B000 - 0x0000000000002840
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: BB25CF6F-F1D4-11D2-9A0C-0090273FC1FD 8988D580
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 8988D620
PROGRESS CODE: V03040003 I0
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
Loading driver 6D33944A-EC75-4855-A54D-809C75241F6C
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89893040
Loading driver at 0x00089824000 EntryPoint=0x00089826926 BdsDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 898A6398
ProtectUefiImageCommon - 0x89893040
- 0x0000000089824000 - 0x0000000000017F80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 665E3FF6-46CC-11D4-9A38-0090273FC14D 8983AB48
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver F2765DEC-6B41-11D5-8E71-00902707B35E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89893A40
Loading driver at 0x00089889000 EntryPoint=0x00089889D0B Timer.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89893418
ProtectUefiImageCommon - 0x89893A40
- 0x0000000089889000 - 0x0000000000001880
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 8988A680
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver 42857F0A-13F2-4B21-8A23-53D3F714B840
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89892040
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/tina/edk2-UDK2017/Build/CorebootPayloadPkgX64/DEBUG_GCC5/X64/MdeModulePkg/Universal/CapsuleRuntimeDxe/CapsuleRuntimeDxe/DEBUG/CapsuleRuntimeDxe.dll !!!!!!!!
Loading driver at 0x00089AED000 EntryPoint=0x00089AED9A2 CapsuleRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89893518
ProtectUefiImageCommon - 0x89892040
- 0x0000000089AED000 - 0x0000000000002CC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 5053697E-2CBC-4819-90D9-0580DEEE5754 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver AD608272-D07F-4964-801E-7BD3B7888652
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89892540
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/tina/edk2-UDK2017/Build/CorebootPayloadPkgX64/DEBUG_GCC5/X64/MdeModulePkg/Universal/MonotonicCounterRuntimeDxe/MonotonicCounterRuntimeDxe/DEBUG/MonotonicCounterRuntimeDxe.dll !!!!!!!!
Loading driver at 0x00089AEB000 EntryPoint=0x00089AEBDAE MonotonicCounterRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89892318
ProtectUefiImageCommon - 0x89892540
- 0x0000000089AEB000 - 0x0000000000001D00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 1DA97072-BDDC-4B30-99F1-72A0B56FFF2A 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver 378D7B65-8DA9-4773-B6E4-A47826A833E1
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898911C0
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/tina/edk2-UDK2017/Build/CorebootPayloadPkgX64/DEBUG_GCC5/X64/PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe/DEBUG/PcRtc.dll !!!!!!!!
Loading driver at 0x00089AE7000 EntryPoint=0x00089AE7AA1 PcRtc.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89891A98
ProtectUefiImageCommon - 0x898911C0
- 0x0000000089AE7000 - 0x0000000000003BC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 27CFAC87-46CC-11D4-9A38-0090273FC14D 0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver EBF342FE-B1D3-4EF8-957C-8048606FF671
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89877CC0
Loading driver at 0x00089809000 EntryPoint=0x00089819B81 SetupBrowser.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89891918
ProtectUefiImageCommon - 0x89877CC0
- 0x0000000089809000 - 0x000000000001AD80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: B9D4C360-BCFB-4F9B-9298-53C136982258 898235F0
InstallProtocolInterface: A770C357-B693-4E6D-A6CF-D21C728E550B 89823620
InstallProtocolInterface: 1F73B18D-4630-43C1-A1DE-6F80855D7DA4 89823600
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver 128FB770-5E79-4176-9E51-9BB268A17DD1
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89869040
Loading driver at 0x0008985C000 EntryPoint=0x0008985C240 PciHostBridgeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89877918
ProtectUefiImageCommon - 0x89869040
- 0x000000008985C000 - 0x000000000000CB00
PROGRESS CODE: V03040002 I0
InitRootBridge: populated root bus 0, with room for 3 subordinate bus(es)
RootBridge: PciRoot(0x0)
Support/Attr: 7001F / 7001F
DmaAbove4G: No
NoExtConfSpace: No
AllocAttr: 0 ()
Bus: 0 - 3
Io: 2000 - 3FFF
Mem: C0000000 - FE0FFFFF
MemAbove4G: FFFFFFFFFFFFFFFF - 0
PMem: FFFFFFFFFFFFFFFF - 0
PMemAbove4G: FFFFFFFFFFFFFFFF - 0
PciHostBridge driver failed to set EFI_MEMORY_UC to MMIO aperture - Out of Resources.
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89869C18
InstallProtocolInterface: 2F707EBB-4A1A-11D4-9A38-0090273FC14D 898696C0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
Loading driver F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89876BC0
Loading driver at 0x00089872000 EntryPoint=0x00089872DB2 WatchdogTimer.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89876098
ProtectUefiImageCommon - 0x89876BC0
- 0x0000000089872000 - 0x0000000000001880
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 665E3FF5-46CC-11D4-9A38-0090273FC14D 89873680
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
Loading driver E660EA85-058E-4B55-A54B-F02F83A24707
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898763C0
Loading driver at 0x000895D4000 EntryPoint=0x000895D86C0 DisplayEngine.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89876998
ProtectUefiImageCommon - 0x898763C0
- 0x00000000895D4000 - 0x0000000000013600
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 9BBE29E9-FDA1-41EC-AD52-452213742D2E 895E52B0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03040003 I0
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
Loading driver 93B80004-9FB3-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 8986F040
Loading driver at 0x000895A8000 EntryPoint=0x000895A90D0 PciBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89870418
ProtectUefiImageCommon - 0x8986F040
- 0x00000000895A8000 - 0x0000000000015140
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895BC740
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895BCA00
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895BC550
InstallProtocolInterface: 19CB87AB-2CB9-4665-8360-DDCF6054F79D 895BC530
PROGRESS CODE: V03040003 I0
Loading driver 51CCF399-4FDF-4E55-A45B-E123F84D456A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 8986F440
Loading driver at 0x00089801000 EntryPoint=0x00089801BA7 ConPlatformDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 8986F818
ProtectUefiImageCommon - 0x8986F440
- 0x0000000089801000 - 0x0000000000003F00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89804B40
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89804CE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89804CC0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89804B00
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89804CE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89804CC0
PROGRESS CODE: V03040003 I0
Loading driver 408EDCEC-CF6D-477C-A5A8-B4844E3DE281
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 8986C940
Loading driver at 0x000895EA000 EntryPoint=0x000895EB1FA ConSplitterDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 8986C198
ProtectUefiImageCommon - 0x8986C940
- 0x00000000895EA000 - 0x0000000000008480
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895F1DE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895F1DA0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895F1A10
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895F1E80
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895F1E40
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895F19F0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895F1F20
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895F1EE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895F19D0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895F1FC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895F1F80
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895F19B0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895F2060
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895F2020
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895F1990
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 895F1AB0
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 895F1AE0
InstallProtocolInterface: 31878C87-0B75-11D5-9A4F-0090273FC14D 895F1B40
InstallProtocolInterface: 8D59D32B-C655-4AE9-9B15-F25904992A43 895F1B98
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 895F20F0
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 895F1C50
PROGRESS CODE: V03040003 I0
Loading driver CCCB0C28-4B24-11D5-9A5A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89808840
Loading driver at 0x000895CE000 EntryPoint=0x000895CE9F8 GraphicsConsoleDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89808718
ProtectUefiImageCommon - 0x89808840
- 0x00000000895CE000 - 0x0000000000005B00
PROGRESS CODE: V03040002 I0
CoreSignalEvent1 = 0
CoreSignalEvent3 = 0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895D21A0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895D38A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895D2170
PROGRESS CODE: V03040003 I0
Loading driver 9E863906-A40F-4875-977F-5B93FF237FC6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89807140
Loading driver at 0x000895BE000 EntryPoint=0x000895BF7A3 TerminalDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89807898
ProtectUefiImageCommon - 0x89807140
- 0x00000000895BE000 - 0x0000000000007DC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895C5A40
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895C5A00
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895C56F0
PROGRESS CODE: V03040003 I0
Loading driver 6B38F7B4-AD98-40E9-9093-ACA2B5A253C4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89806040
Loading driver at 0x000895C9000 EntryPoint=0x000895CA302 DiskIoDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89806D98
ProtectUefiImageCommon - 0x89806040
- 0x00000000895C9000 - 0x0000000000004900
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895CD5E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895CD720
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895CD5B0
PROGRESS CODE: V03040003 I0
Loading driver 1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89806440
Loading driver at 0x0008959C000 EntryPoint=0x0008959F0AA PartitionDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89806698
ProtectUefiImageCommon - 0x89806440
- 0x000000008959C000 - 0x0000000000005EC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895A1CA0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895A1C20
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895A1C80
PROGRESS CODE: V03040003 I0
Loading driver CD3BAFB6-50FB-4FE8-8E4E-AB74D2C1A600
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 89805B40
Loading driver at 0x000895F6000 EntryPoint=0x000895F6E73 EnglishDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89806898
ProtectUefiImageCommon - 0x89805B40
- 0x00000000895F6000 - 0x0000000000001BC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 1D85CD7F-F43D-11D2-9A0C-0090273FC14D 895F76A0
InstallProtocolInterface: A4C751FC-23AE-4C3E-92E9-4964CF63F349 895F7640
PROGRESS CODE: V03040003 I0
Loading driver 8F4CD826-A5A0-4E93-9522-CFB0AB72926C
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 898052C0
Loading driver at 0x000895C6000 EntryPoint=0x000895C7522 SataController.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 89805618
ProtectUefiImageCommon - 0x898052C0
- 0x00000000895C6000 - 0x0000000000002B40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895C8960
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895C8920
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895C88B0
PROGRESS CODE: V03040003 I0
Loading driver 19DF145A-B1D4-453F-8507-38816676D7F6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895FBD40
Loading driver at 0x0008958E000 EntryPoint=0x0008958EEB5 AtaBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895FB918
ProtectUefiImageCommon - 0x895FBD40
- 0x000000008958E000 - 0x00000000000069C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89594780
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89594740
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89594500
PROGRESS CODE: V03040003 I0
Loading driver 5E523CB4-D397-4986-87BD-A6DD8B22F455
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895FB3C0
Loading driver at 0x00089579000 EntryPoint=0x0008957BAD5 AtaAtapiPassThruDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895FB718
ProtectUefiImageCommon - 0x895FB3C0
- 0x0000000089579000 - 0x000000000000A000
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89582E00
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89582DC0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89582AF0
PROGRESS CODE: V03040003 I0
Loading driver 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895FA140
Loading driver at 0x00089598000 EntryPoint=0x00089599041 ScsiBus.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895FAC18
ProtectUefiImageCommon - 0x895FA140
- 0x0000000089598000 - 0x0000000000003880
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 8959B620
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 8959B6C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 8959B5F0
PROGRESS CODE: V03040003 I0
Loading driver 0A66E322-3740-4CCE-AD62-BD172CECCA35
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895FA640
Loading driver at 0x0008956F000 EntryPoint=0x00089570176 ScsiDisk.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895F5018
ProtectUefiImageCommon - 0x895FA640
- 0x000000008956F000 - 0x0000000000009900
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89578700
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895786C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89578630
PROGRESS CODE: V03040003 I0
Loading driver 961578FE-B6B7-44C3-AF35-6BC705CD2B1F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895F5140
Loading driver at 0x00089564000 EntryPoint=0x00089565151 Fat.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895F5C18
ProtectUefiImageCommon - 0x895F5140
- 0x0000000089564000 - 0x000000000000A7C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 8956E620
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 8956E600
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 8956E3F0
PROGRESS CODE: V03040003 I0
Loading driver 8E325979-3FE1-4927-AAE2-8F5C4BD2AF0D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895F55C0
Loading driver at 0x0008955A000 EntryPoint=0x00089560464 SdMmcPciHcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895F4F98
ProtectUefiImageCommon - 0x895F55C0
- 0x000000008955A000 - 0x0000000000009280
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89563020
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89562FE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89563100
PROGRESS CODE: V03040003 I0
Loading driver 2145F72F-E6F1-4440-A828-59DC9AAB5F89
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895F48C0
Loading driver at 0x00089551000 EntryPoint=0x00089557065 EmmcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895F4218
ProtectUefiImageCommon - 0x895F48C0
- 0x0000000089551000 - 0x0000000000008500
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895592C0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89559280
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 895593D0
PROGRESS CODE: V03040003 I0
Loading driver 430AC2F7-EEC6-4093-94F7-9F825A7C1C40
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895F3040
Loading driver at 0x00089588000 EntryPoint=0x00089589202 SdDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895F4398
ProtectUefiImageCommon - 0x895F3040
- 0x0000000089588000 - 0x0000000000005E40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 8958DCA0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 8958DC60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 8958DA30
PROGRESS CODE: V03040003 I0
Loading driver 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895F3A40
Loading driver at 0x00089541000 EntryPoint=0x00089545E2D UhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895F3898
ProtectUefiImageCommon - 0x895F3A40
- 0x0000000089541000 - 0x00000000000076C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895484E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895484A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89548440
PROGRESS CODE: V03040003 I0
Loading driver BDFE430E-8F2A-4DB0-9991-6F856594777E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895E9040
Loading driver at 0x0008952D000 EntryPoint=0x0008952E953 EhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895E9D18
ProtectUefiImageCommon - 0x895E9040
- 0x000000008952D000 - 0x0000000000009300
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 895360E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895360A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89536130
PROGRESS CODE: V03040003 I0
Loading driver B7F50E91-A759-412C-ADE4-DCD03E7F7C28
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895E9440
Loading driver at 0x00089511000 EntryPoint=0x000895146FE XhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895E9318
ProtectUefiImageCommon - 0x895E9440
- 0x0000000089511000 - 0x000000000000D7C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 8951E520
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 8951E4E0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 8951E650
PROGRESS CODE: V03040003 I0
Loading driver 240612B7-A063-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895E8040
Loading driver at 0x00089523000 EntryPoint=0x00089524219 UsbBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895E8E18
ProtectUefiImageCommon - 0x895E8040
- 0x0000000089523000 - 0x0000000000009980
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 8952C720
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 8952C600
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 8952C5B0
PROGRESS CODE: V03040003 I0
Loading driver 2D2E62CF-9ECF-43B7-8219-94E7FC713DFE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895E8440
Loading driver at 0x0008953A000 EntryPoint=0x0008953AD6C UsbKbDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895E8318
ProtectUefiImageCommon - 0x895E8440
- 0x000000008953A000 - 0x0000000000006900
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89540700
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 895406C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89540640
PROGRESS CODE: V03040003 I0
Loading driver 9FB4B4A7-42C0-4BCD-8540-9BCC6711F83E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895A7B40
Loading driver at 0x0008950B000 EntryPoint=0x0008950EA41 UsbMassStorageDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895E8918
ProtectUefiImageCommon - 0x895A7B40
- 0x000000008950B000 - 0x0000000000005DC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89510BE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89510A20
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89510BC0
PROGRESS CODE: V03040003 I0
Loading driver 4ACA697E-F883-446F-98F7-096416FFFFFF
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895A72C0
Loading driver at 0x000894F9000 EntryPoint=0x000894FA4AA OhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895A7618
ProtectUefiImageCommon - 0x895A72C0
- 0x00000000894F9000 - 0x0000000000008100
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89500F00
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89500EC0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89500E70
PROGRESS CODE: V03040003 I0
Loading driver 0B04B2ED-861C-42CD-A22F-C3AAFACCB896
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 895A6D40
Loading driver at 0x00089584000 EntryPoint=0x00089584E94 FbGop.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 895A6B18
ProtectUefiImageCommon - 0x895A6D40
- 0x0000000089584000 - 0x0000000000003F40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 89587CA0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 89587D60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 89587C70
PROGRESS CODE: V03040003 I0
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V03041001 I0
[Bds] Entry...
[BdsDxe] Locate Variable Lock protocol - Not Found
Variable Driver Auto Update Lang, Lang:eng, PlatformLang:en
PROGRESS CODE: V03051005 I0
PROGRESS CODE: V02010000 I0
PciBus: Discovered PCI @ [00|00|00]

PciBus: Discovered PCI @ [00|02|00]
BAR[0]: Type = Mem64; Alignment = 0xFFFFFF; Length = 0x1000000; Offset = 0x10
BAR[1]: Type = PMem64; Alignment = 0xFFFFFFF; Length = 0x10000000; Offset = 0x18
BAR[2]: Type = Io16; Alignment = 0x3F; Length = 0x40; Offset = 0x20

PciBus: Discovered PCI @ [00|08|00]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|12|00]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|14|00]
BAR[0]: Type = Mem64; Alignment = 0xFFFF; Length = 0x10000; Offset = 0x10

PciBus: Discovered PCI @ [00|14|02]
BAR[0]: Type = Mem64; Alignment = 0x1FFF; Length = 0x2000; Offset = 0x10
BAR[1]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x18

PciBus: Discovered PCI @ [00|14|05]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|15|00]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|15|01]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|17|00]
BAR[0]: Type = Mem32; Alignment = 0x1FFF; Length = 0x2000; Offset = 0x10
BAR[1]: Type = Mem32; Alignment = 0xFFF; Length = 0x100; Offset = 0x14
BAR[2]: Type = Io16; Alignment = 0x7; Length = 0x8; Offset = 0x18
BAR[3]: Type = Io16; Alignment = 0x3; Length = 0x4; Offset = 0x1C
BAR[4]: Type = Io16; Alignment = 0x1F; Length = 0x20; Offset = 0x20
BAR[5]: Type = Mem32; Alignment = 0xFFF; Length = 0x800; Offset = 0x24

PciBus: Discovered PPB @ [00|1B|00]

PciBus: Discovered PCI @ [01|00|00]
BAR[0]: Type = Mem64; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x10

PciBus: Discovered PPB @ [00|1B|04]

PciBus: Discovered PCI @ [02|00|00]
BAR[0]: Type = Mem32; Alignment = 0x7FFFF; Length = 0x80000; Offset = 0x10
BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18
BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C

PciBus: Discovered PCI @ [02|00|01]
BAR[0]: Type = Mem32; Alignment = 0x7FFFF; Length = 0x80000; Offset = 0x10
BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18
BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C

PciBus: Discovered PCI @ [02|00|02]
BAR[0]: Type = Mem32; Alignment = 0x7FFFF; Length = 0x80000; Offset = 0x10
BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18
BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C

PciBus: Discovered PCI @ [02|00|03]
BAR[0]: Type = Mem32; Alignment = 0x7FFFF; Length = 0x80000; Offset = 0x10
BAR[2]: Type = Io32; Alignment = 0x1F; Length = 0x20; Offset = 0x18
BAR[3]: Type = Mem32; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x1C

PciBus: Discovered PPB @ [00|1D|00]

PciBus: Discovered PCI @ [00|1E|00]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10
BAR[1]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x18

PciBus: Discovered PCI @ [00|1E|01]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|1E|02]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10
BAR[1]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x18

PciBus: Discovered PCI @ [00|1E|03]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10
BAR[1]: Type = Mem64; Alignment = 0xFFF; Length = 0x1000; Offset = 0x18

PciBus: Discovered PCI @ [00|1F|00]

PciBus: Discovered PCI @ [00|1F|03]
BAR[0]: Type = Mem64; Alignment = 0x3FFF; Length = 0x4000; Offset = 0x10
BAR[3]: Type = Mem64; Alignment = 0xFFFFF; Length = 0x100000; Offset = 0x20

PciBus: Discovered PCI @ [00|1F|04]
BAR[0]: Type = Mem64; Alignment = 0xFFF; Length = 0x100; Offset = 0x10
BAR[3]: Type = Io16; Alignment = 0x1F; Length = 0x20; Offset = 0x20

PciBus: Discovered PCI @ [00|1F|05]
BAR[0]: Type = Mem32; Alignment = 0xFFF; Length = 0x1000; Offset = 0x10

PciBus: Discovered PCI @ [00|1F|06]
BAR[0]: Type = Mem32; Alignment = 0x1FFFF; Length = 0x20000; Offset = 0x10

InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A6618
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A51A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A6698
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A56A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A5598
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A4028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A6718
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A4428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A5618
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A4828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A4E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A3028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A4F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A3428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A4F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A3828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A3E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A2028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A3F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A2428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A3F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 895A2828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A2E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89597028
PROGRESS CODE: V02010004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A2F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89597428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 895A2F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89597828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89597E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89596028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89597F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89596428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89597F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89596828
PROGRESS CODE: V02010004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89596E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89595028
PROGRESS CODE: V02010004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89596F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89595428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89596F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89595828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89595E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89583028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89595F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89583428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89595F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89583828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89583E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89550028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89583F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89550428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89583F18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 89550828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89550E98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 8954F028
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
Found PCI VGA device
GOP START
PROGRESS CODE: V01030004 I0
PROGRESS CODE: V02010004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 8954C218
FbGopCheckForVbe - Success
InstallProtocolInterface: 9042A9DE-23DC-4A38-96FB-7ADED080516A 8954C9B0
InstallProtocolInterface: 1C0C34F6-D380-41FA-A049-8AD06C1A66AA 8954C9D0
InstallProtocolInterface: BD8C1056-9F36-44EC-92A8-A6337F817986 8954C9E0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
Found LPC Bridge device
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
InstallReadyToLock entering......
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
All EndOfDxe callbacks have returned successfully
InstallReadyToLock end
[Bds]RegisterKeyNotify: 000C/0000 80000000/00 Success
[Bds]RegisterKeyNotify: 0002/0000 80000000/00 Success
[Bds]RegisterKeyNotify: 0000/000D 80000000/00 Success
GraphicsConsole video resolution 1920 x 1080
Graphics - Mode 0, Column = 80, Row = 25
Graphics - Mode 1, Column = 80, Row = 50
Graphics - Mode 2, Column = 100, Row = 31
Graphics - Mode 3, Column = 240, Row = 56
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 8954A230
InstallProtocolInterface: D3B36F2C-D551-11D4-9A46-0090273FC14D 0
InstallProtocolInterface: 9042A9DE-23DC-4A38-96FB-7ADED080516A 895F2180
Terminal - Mode 0, Column = 80, Row = 25
Terminal - Mode 1, Column = 80, Row = 50
Terminal - Mode 2, Column = 100, Row = 31
[=3hPROGRESS CODE: V01040001 I0
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 89549440
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 89549528
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 89549458
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 89549818
InstallProtocolInterface: D3B36F2C-D551-11D4-9A46-0090273FC14D 0
InstallProtocolInterface: D3B36F2D-D551-11D4-9A46-0090273FC14D 0
[=3h[=3hInstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
XhcCreateUsb3Hc: Capability length 0x80
XhcCreateUsb3Hc: HcSParams1 0x1A000840
XhcCreateUsb3Hc: HcSParams2 0x14200054
XhcCreateUsb3Hc: HcCParams 0x200077C1
XhcCreateUsb3Hc: DBOff 0x3000
XhcCreateUsb3Hc: RTSOff 0x2000
XhcCreateUsb3Hc: UsbLegSupOffset 0x46C
XhcCreateUsb3Hc: DebugCapSupOffset 0x700
XhcSetBiosOwnership: called to set BIOS ownership
XhcResetHC!
XhcInitSched:DCBAA=0x88CB3000
XhcInitSched:XHC_CRCR=0x88CB3240
XhcInitSched:XHC_EVENTRING=0x88CB4240
InstallProtocolInterface: 3E745226-9818-45B6-A2AC-D7CD0E8BA2BC 88CC3038
XhcDriverBindingStart: XHCI started for controller @ 89595E18
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020004 I0
InstallProtocolInterface: 240612B7-A063-11D4-9A3A-0090273FC14D 88C98020
PROGRESS CODE: V02020003 I0
XhcGetCapability: 26 ports, 64 bit 1
UsbRootHubInit: root hub 88C98C98 - max speed 3, 26 ports
CoreSignalEvent1 = 0
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 3 state - 201, change - 01 on 88C98C98
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: new device connected at port 3
XhcUsbPortReset!
XhcSetRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
Enable Slot Successfully, The Slot ID = 0x1
Address 1 assigned successfully
UsbEnumerateNewDev: hub port 3 is reset
UsbEnumerateNewDev: device is of 1 speed
UsbEnumerateNewDev: device uses translator (0, 0)
UsbEnumerateNewDev: device is now ADDRESSED at 1
UsbEnumerateNewDev: max packet size for EP 0 is 8
Evaluate context
UsbBuildDescTable: device has 1 configures
UsbGetOneConfig: total length is 59
UsbParseConfigDesc: config 1 has 2 interfaces
UsbParseInterfaceDesc: interface 0(setting 0) has 1 endpoints
UsbParseInterfaceDesc: interface 1(setting 0) has 1 endpoints
Configure Endpoint
UsbEnumerateNewDev: device 1 is now in CONFIGED state
UsbSelectConfig: config 1 selected for device 1
UsbSelectSetting: setting 0 selected for interface 0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88C97A18
InstallProtocolInterface: 2B2F68D6-0CD2-44CF-8E8B-BBA20B1B5B75 88C96EC0
UsbConnectDriver: TPL before connect is 8, 88C97898
PROGRESS CODE: V01010004 I0
PROGRESS CODE: V01010003 I0
PROGRESS CODE: V01010006 I0
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 88C971B8
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 88C971D0
CoreSignalEvent1 = 0
CoreSignalEvent2 = 0
CoreSignalEvent3 = 0
PROGRESS CODE: V01010001 I0
PROGRESS CODE: V01011001 I0
InstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0
UsbConnectDriver: TPL after connect is 8
UsbSelectSetting: setting 0 selected for interface 1
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88C91A98
InstallProtocolInterface: 2B2F68D6-0CD2-44CF-8E8B-BBA20B1B5B75 88C918C0
UsbConnectDriver: TPL before connect is 8, 88C91998
UsbConnectDriver: TPL after connect is 8
UsbSelectConfig: failed to connect driver Not Found, ignored
PROGRESS CODE: V02020006 I0
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 4 state - 01, change - 01 on 88C98C98
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: new device connected at port 4
XhcUsbPortReset!
XhcSetRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
Enable Slot Successfully, The Slot ID = 0x2
Address 2 assigned successfully
UsbEnumerateNewDev: hub port 4 is reset
UsbEnumerateNewDev: device is of 0 speed
UsbEnumerateNewDev: device uses translator (0, 0)
UsbEnumerateNewDev: device is now ADDRESSED at 2
Evaluate context
UsbEnumerateNewDev: max packet size for EP 0 is 64
Evaluate context
UsbBuildDescTable: device has 1 configures
UsbGetOneConfig: total length is 200
UsbParseConfigDesc: config 1 has 2 interfaces
UsbParseInterfaceDesc: interface 0(setting 0) has 3 endpoints
UsbParseInterfaceDesc: interface 1(setting 0) has 2 endpoints
UsbParseInterfaceDesc: interface 1(setting 1) has 2 endpoints
UsbParseInterfaceDesc: interface 1(setting 2) has 2 endpoints
UsbParseInterfaceDesc: interface 1(setting 3) has 2 endpoints
UsbParseInterfaceDesc: interface 1(setting 4) has 2 endpoints
UsbParseInterfaceDesc: interface 1(setting 5) has 2 endpoints
UsbParseInterfaceDesc: interface 1(setting 6) has 2 endpoints
XhcInitializeEndpointContext: Unsupport ISO EP found, Transfer ring is not allocated.
XhcInitializeEndpointContext: Unsupport ISO EP found, Transfer ring is not allocated.
Configure Endpoint
UsbEnumerateNewDev: device 2 is now in CONFIGED state
UsbSelectConfig: config 1 selected for device 2
UsbSelectSetting: setting 0 selected for interface 0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88C8EA18
InstallProtocolInterface: 2B2F68D6-0CD2-44CF-8E8B-BBA20B1B5B75 88C8E840
UsbConnectDriver: TPL before connect is 8, 88C8E718
UsbConnectDriver: TPL after connect is 8
UsbSelectConfig: failed to connect driver Not Found, ignored
UsbSelectSetting: setting 0 selected for interface 1
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88C8E698
InstallProtocolInterface: 2B2F68D6-0CD2-44CF-8E8B-BBA20B1B5B75 88C8E4C0
UsbConnectDriver: TPL before connect is 8, 88C8E598
UsbConnectDriver: TPL after connect is 8
UsbSelectConfig: failed to connect driver Not Found, ignored
PROGRESS CODE: V02020006 I0
CoreSignalEvent3 = 0
UsbBusStart: usb bus started on 89595E18, root hub 88C98C98
SdMmcPciHcDriverBindingStart: Start
== Slot [0] Capability is 0x88C8D170 ==
Timeout Clk Freq 1MHz
Base Clk Freq 200MHz
Max Blk Len 512bytes
8-bit Support FALSE
ADMA2 Support TRUE
HighSpeed Support TRUE
SDMA Support TRUE
Suspend/Resume FALSE
Voltage 3.3 TRUE
Voltage 3.0 FALSE
Voltage 1.8 TRUE
64-bit Sys Bus TRUE
Async Interrupt TRUE
SlotType Removable Slot
SDR50 Support TRUE
SDR104 Support TRUE
DDR50 Support TRUE
Driver Type A FALSE
Driver Type C FALSE
Driver Type D FALSE
Driver Type 4 FALSE
Retuning TimerCnt 14seconds
SDR50 Tuning FALSE
Retuning Mode Mode 1
Clock Multiplier M = 1
HS 400 FALSE
SdMmcHcCardDetect: No device attached in Slot[0]!!!
InstallProtocolInterface: 716EF0D9-FF83-4F69-81E9-518BD39A8E70 88C8D0B0
SdMmcPciHcDriverBindingStart: Success End on 89597E18
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 88C89018
InstallProtocolInterface: 430AC2F7-EEC6-4093-94F7-9F825A7C1C40 88C8D718
SataControllerStart START
InstallProtocolInterface: A1E37052-80D9-4E65-A317-3E9A55C43EC9 88C8D320
SataControllerStart END status = Success
==AtaAtapiPassThru Start== Controller = 895A4D98
PROGRESS CODE: V02010004 I0
port [0] port mulitplier [0] has a [harddisk]
Enabled S.M.A.R.T feature at port [0] PortMultiplier [0]!
CalculateBestPioMode: AdvancedPioMode = 3
IdeInitCalculateMode: PioMode = 4
CalculateBestUdmaMode: DeviceUDmaMode = 7F
IdeInitCalculateMode: UdmaMode = 5
PROGRESS CODE: V01070004 I0
InstallProtocolInterface: 1D3DE7F0-0807-424F-AA69-11A54E19A46F 88C8B040
InstallProtocolInterface: 143B7632-B81B-4CB7-ABD3-B625A5B9BFFE 88C8B090
PROGRESS CODE: V02080000 I0
InstallProtocolInterface: 19DF145A-B1D4-453F-8507-38816676D7F6 88C8B518
PROGRESS CODE: V02080003 I0
PROGRESS CODE: V02080004 I0
AtaBus - Identify Device: Port 0 PortMultiplierPort FFFF
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88C8B598
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 88B87028
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 88B87058
InstallProtocolInterface: D432A67F-14DC-484B-B3BB-3F0291849327 88B870B0
PROGRESS CODE: V02070000 I0
InstallProtocolInterface: 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B 88B87C20
PROGRESS CODE: V02070003 I0
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 88C8C020
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 88C8C038
BlockSize : 512
LastBlock : 75FFFFF
Valid efi partition table header
Valid efi partition table header
Valid primary and Valid backup partition table
Partition entries read block success
Number of partition entries: 128
start check partition entries
End check partition entries
Index : 0
Start LBA : 800
End LBA : 1007FF
Partition size: 100000
Start : 100000 End : 200FFE00
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88B7CE98
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 88B7C330
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 88B7C360
InstallProtocolInterface: C12A7328-F81F-11D2-BA4B-00A0C93EC93B 0
Index : 1
Start LBA : 100800
End LBA : 75FF7FF
Partition size: 74FF000
Start : 20100000 End : EBFEFFE00
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 88B7C618
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 88B7C730
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 88B7C760
Prepare to Free Pool
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 88B76B20
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 88B76B38
BlockSize : 512
LastBlock : FFFFF
InstallProtocolInterface: 964E5B22-6459-11D2-8E39-00A0C969723B 88B7B030
Installed Fat filesystem on 88B7C898
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 88B7C120
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 88B7C138
BlockSize : 512
LastBlock : 74FEFFF
PROGRESS CODE: V02020000 I0
UsbBusRecursivelyConnectWantedUsbIo: TPL before connect is 4
UsbBusRecursivelyConnectWantedUsbIo: TPL after connect is 4
UsbBusRecursivelyConnectWantedUsbIo: TPL before connect is 4
UsbBusRecursivelyConnectWantedUsbIo: TPL after connect is 4
UsbBusRecursivelyConnectWantedUsbIo: TPL before connect is 4
UsbBusRecursivelyConnectWantedUsbIo: TPL after connect is 4
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 886E1018
InstallProtocolInterface: 430AC2F7-EEC6-4093-94F7-9F825A7C1C40 88C98A98
PROGRESS CODE: V02080000 I0
PROGRESS CODE: V02080003 I0
SataControllerStart START
SataControllerStart error return status = Already started
PROGRESS CODE: V02070000 I0
PROGRESS CODE: V02070003 I0
BlockSize : 512
LastBlock : 75FFFFF
Valid efi partition table header
Valid efi partition table header
Valid primary and Valid backup partition table
Partition entries read block success
Number of partition entries: 128
start check partition entries
End check partition entries
Index : 0
Start LBA : 800
End LBA : 1007FF
Partition size: 100000
Start : 100000 End : 200FFE00
Index : 1
Start LBA : 100800
End LBA : 75FF7FF
Partition size: 74FF000
Start : 20100000 End : EBFEFFE00
Prepare to Free Pool
BlockSize : 512
LastBlock : 74FEFFF

F2 or Down to enter Boot Manager Menu.
ENTER to boot directly.

[Bds]OsIndication: 0000000000000000
[Bds]=============Begin Load Options Dumping ...=============
Driver Options:
SysPrep Options:
Boot Options:
Boot0000: UiApp 0x0109
Boot0001: UEFI SM659GXC CDZ A0519022617060000001 0x0001
Boot0002: UEFI Shell 0x0001
PlatformRecovery Options:
PlatformRecovery0000: Default PlatformRecovery 0x0001
[Bds]=============End Load Options Dumping=============
[Bds]BdsWait ...Zzzzzzzzzzzz...
[Bds]BdsWait(3)..Zzzz...
CoreWaitForEvent = 0
CoreWaitForEvent = 1
CoreWaitForEvent1 = 2
CoreSignalEvent1 = 0


How to link DXE_DRIVER from UEFI_APPLICATION?

joseph@...
 

Hi,

I want to include Tcg2PhysicalPresenceLib in my UEFI Application.

Tcg2PhysicalPresenceLib is located in SecurityPkg/Library/Tpm2DeviceLibTcg2/Tpm2DeviceLibTcg2.inf in EDK2.

========================================
This is what I tried:

Package dsc:
[LibraryClasses.common]
Tpm2DeviceLibTcg2|SecurityPkg/Library/Tpm2DeviceLibTcg2/Tpm2DeviceLibTcg2.inf

Application inf:
[LibraryClasses]
Tcg2PhysicalPresenceLib
========================================

If you do the above, you will get this error.

.../edk2/MyPkg/MyPkg.dsc(...): error 1001: Module type [UEFI_APPLICATION] is not supported by library instance [.../edk2/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf]
consumed by [.../edk2/MyPkg/MyApp/MyApp.inf]

How do I use Tcg2PhysicalPresenceLib in Application?

Kind regards,
Joseph


Re: 回复: [edk2-discuss] what's the conditions of submodule updating

wenyi,xie
 

OK, I got it. Thank you.

Thanks
Wenyi

On 2021/2/5 11:15, gaoliming wrote:
Yes. Most update depends on the real request.

Thanks
Liming
-----邮件原件-----
发件人: bounce+34241+499+4905953+8764802@groups.io
<bounce+34241+499+4905953+8764802@groups.io> 代表 Laszlo Ersek
发送时间: 2021年2月2日 19:09
收件人: discuss@edk2.groups.io; xiewenyi2@huawei.com
主题: Re: [edk2-discuss] what's the conditions of submodule updating

On 02/02/21 03:14, wenyi,xie via groups.io wrote:
Hi all,
May I ask a question.
In what conditions will we update submodules. Will we update the
sbumodule when it only fixes a vulnerability, or any other conditions should be
meet before updating.

I don't think we've formalized this. I would think: we update a
submodule when there's a reason to. Important bugfix (security or
otherwise), or a new feature that we'd like to consume in an edk2 module.

Just my impressions.

Thanks
Laszlo






.


回复: [edk2-discuss] what's the conditions of submodule updating

gaoliming
 

Yes. Most update depends on the real request.

Thanks
Liming

-----邮件原件-----
发件人: bounce+34241+499+4905953+8764802@groups.io
<bounce+34241+499+4905953+8764802@groups.io> 代表 Laszlo Ersek
发送时间: 2021年2月2日 19:09
收件人: discuss@edk2.groups.io; xiewenyi2@huawei.com
主题: Re: [edk2-discuss] what's the conditions of submodule updating

On 02/02/21 03:14, wenyi,xie via groups.io wrote:
Hi all,
May I ask a question.
In what conditions will we update submodules. Will we update the
sbumodule when it only fixes a vulnerability, or any other conditions should be
meet before updating.

I don't think we've formalized this. I would think: we update a
submodule when there's a reason to. Important bugfix (security or
otherwise), or a new feature that we'd like to consume in an edk2 module.

Just my impressions.

Thanks
Laszlo





回复: [edk2-discuss] 回复: [edk2-discuss] edk2 build failure due to long paths

gaoliming
 

Can you attach the log of the bios build log to generate RELEASE_GCC5/AARCH64/Sbsa.efi?

Seemly, this EFI image is not generated.

Thanks
Liming

-----邮件原件-----
发件人: bounce+34241+517+4905953+8764802@groups.io
<bounce+34241+517+4905953+8764802@groups.io> 代表
rajesh.ravi@broadcom.com via groups.io
发送时间: 2021年2月5日 5:43
收件人: rajesh.ravi@broadcom.com; discuss@edk2.groups.io
主题: Re: [edk2-discuss] 回复: [edk2-discuss] edk2 build failure due to long
paths

I'm seeing the same error even after picking the commit id:
020ec963048340c9eaf9799471167d769239bcfc by updating edk2 repository.
i.e. I'm seeing Yocto build failures only when path length is long due to
platform name being slightly longer by a some 10-15 characters more.
Same repository build is passing with Yocto for platform whose name length is
smaller by some 0-15 characters

*Error Log*
-----------------
Thu Feb 4 08:34:24 2021: | ERROR: Execution of
'/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm
9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+
<--f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fb
a_61687168fe-r0/temp/run.do_deploy.19127' failed with exit code 1:
Thu Feb 4 08:34:24 2021: | install: cannot stat
'/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm
9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+
<--f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fb
a_61687168fe-r0/git/Build/StingrayPkg/RELEASE_GCC5/AARCH64/Sbsa.efi':
No such file or directory
Thu Feb 4 08:34:24 2021: | WARNING: exit code 1 from a shell command.
Thu Feb 4 08:34:24 2021: |-
Thu Feb 4 08:34:24 2021: NOTE: recipe
brcm-edk2-gitAUTOINC+f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_3
1754d4ffc_e2e09d9fba_61687168fe-r0: task do_deploy: Failed
Thu Feb 4 08:34:24 2021: ERROR: Task
(mc:stingray:/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/../
meta-brcm/common/recipes-bsp/edk2/brcm-edk2.bb:do_deploy) failed with
exit code '1'

Regards,
Rajesh




Re: 回复: [edk2-discuss] edk2 build failure due to long paths

rajesh.ravi@broadcom.com
 

Following is the corrected error log by removing unwanted/misleading spaces.

*Error Log*
-----------------
Thu Feb 4 08:34:24 2021: | ERROR: Execution of '/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0/temp/run.do_deploy.19127' failed with exit code 1:
Thu Feb 4 08:34:24 2021: | install: cannot stat '/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0/git/Build/StingrayPkg/RELEASE_GCC5/AARCH64/Sbsa.efi': No such file or directory
Thu Feb 4 08:34:24 2021: | WARNING: exit code 1 from a shell command.
Thu Feb 4 08:34:24 2021: |-
Thu Feb 4 08:34:24 2021: NOTE: recipe brcm-edk2-gitAUTOINC+f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0: task do_deploy: Failed
Thu Feb 4 08:34:24 2021: ERROR: Task (mc:stingray:/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/../meta-brcm/common/recipes-bsp/edk2/brcm-edk2.bb:do_deploy) failed with exit code '1'

Regards,
Rajesh

On Thu, Feb 4, 2021 at 01:42 PM, rajesh.ravi@broadcom.com wrote:


*Error Log*
-----------------
Thu Feb 4 08:34:24 2021: | ERROR: Execution of
'/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+
<--f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0/temp/run.do_deploy.19127'
failed with exit code 1:
Thu Feb 4 08:34:24 2021: | install: cannot stat
'/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+
<--f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0/git/Build/StingrayPkg/RELEASE_GCC5/AARCH64/Sbsa.efi':
No such file or directory
Thu Feb 4 08:34:24 2021: | WARNING: exit code 1 from a shell command.
Thu Feb 4 08:34:24 2021: |-
Thu Feb 4 08:34:24 2021: NOTE: recipe
brcm-edk2-gitAUTOINC+f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0:
task do_deploy: Failed
Thu Feb 4 08:34:24 2021: ERROR: Task
(mc:stingray:/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/../meta-brcm/common/recipes-bsp/edk2/brcm-edk2.bb:do_deploy)
failed with exit code '1'


Re: 回复: [edk2-discuss] edk2 build failure due to long paths

rajesh.ravi@broadcom.com
 

I'm seeing the same error even after picking the commit id: 020ec963048340c9eaf9799471167d769239bcfc by updating edk2 repository.
i.e. I'm seeing Yocto build failures only when path length is long due to platform name being slightly longer by a some 10-15 characters more.
Same repository build is passing with Yocto for platform whose name length is smaller by some 0-15 characters

*Error Log*
-----------------
Thu Feb 4 08:34:24 2021: | ERROR: Execution of '/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+ <--f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0/temp/run.do_deploy.19127' failed with exit code 1:
Thu Feb 4 08:34:24 2021: | install: cannot stat '/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/tmp/work/bcm9xxxxi-poky-linux/brcm-edk2/gitAUTOINC+ <--f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0/git/Build/StingrayPkg/RELEASE_GCC5/AARCH64/Sbsa.efi': No such file or directory
Thu Feb 4 08:34:24 2021: | WARNING: exit code 1 from a shell command.
Thu Feb 4 08:34:24 2021: |-
Thu Feb 4 08:34:24 2021: NOTE: recipe brcm-edk2-gitAUTOINC+f30940e557_56f32f8dd9_3574ef9b13_31754d4ffc_31754d4ffc_e2e09d9fba_61687168fe-r0: task do_deploy: Failed
Thu Feb 4 08:34:24 2021: ERROR: Task (mc:stingray:/tmp/yocto_builds/20519231_s9xxxx-bcm9xxxxi/poky/build/../meta-brcm/common/recipes-bsp/edk2/brcm-edk2.bb:do_deploy) failed with exit code '1'

Regards,
Rajesh

361 - 380 of 889