© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It looks like that firmware block the return to the efi_runtime driver for the runtime service tests.
The runtime service provided by the firmware should not block the return, even if the bad parameters were brought to it.
It should return with the errors, like EFI_INVALID_
Like comment from Conlin, the uefi runtime variable interfaces fail will cause the UEFI variable can not be setting and deleteing, it will affect UEFI boot, bootpath, secure boot ... etc.
The test stop at the first subtest of uefirtvariable, on this test it will set variable and then get variable through the uefi runtime service interfaces SetVariable, GetVariable. It is helpful if other Runtime service interfaces could be tested. Such as
sudo fwts uefirttime -- testing the Settime and Gettime interfaces
efibootmgr can be used to add the bootpath variable via efivar driver provided interfacse, but actually will use the runtime service SetVariable provides by the firmware. It should be useful to add a bootpath variable by efibootmgr to see if it work normal.