diff options
author | Tan, Ming <ming.tan@intel.com> | 2020-12-18 12:50:46 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2020-12-22 08:23:51 +0000 |
commit | d4945b102730a54f58be6bda3369c6844565b7ee (patch) | |
tree | 607263b757851a42a76d95da3033bf3a02b99785 /OvmfPkg/MptScsiDxe | |
parent | d77f9b1efff816522d10b34a68114f6ec34488dd (diff) | |
download | edk2-d4945b102730a54f58be6bda3369c6844565b7ee.tar.gz edk2-d4945b102730a54f58be6bda3369c6844565b7ee.tar.bz2 edk2-d4945b102730a54f58be6bda3369c6844565b7ee.zip |
MdeModulePkg/Universal/StatusCodeHandler: Fix a bug about log lost
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3126
1. If use PeiDxeDebugLibReportStatusCode as DebugLib, then some logs
after ExitBootService() will be lost.
2. The root cause:
2.1 The original code will register an unregister function
of gEfiEventExitBootServicesGuid, this unregister function will call
EFI_RSC_HANDLER_PROTOCOL->Unregister and does not support log through
serial port.
2.2 And some other drivers also register call back funtions of
gEfiEventExitBootServicesGuid.
2.3 Then after the unregister function is called, other call back
functions can't out log if them use RSC as DebugLib.
3. The DxeMain will report status code EFI_SW_BS_PC_EXIT_BOOT_SERVICES
after notify all the call back functions of
gEfiEventExitBootServicesGuid.
4. Solution: the StatusCodeHandlerRuntimeDxe.c will not register an
unregister function of gEfiEventExitBootServicesGuid, but unregister it
after receive the status code of EFI_SW_BS_PC_EXIT_BOOT_SERVICES.
Cc: Dandan Bi <dandan.bi@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Ming Tan <ming.tan@intel.com>
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
Reviewed-by: Dandan Bi <dandan.bi@intel.com>
Diffstat (limited to 'OvmfPkg/MptScsiDxe')
0 files changed, 0 insertions, 0 deletions