© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The test is exercising the UEFI run time get variable service. The fact that it locks up in an ioctl shows that the control has been passed from fwts to the kernel and the kernel has passed control over to the UEFI run time service and this never returned.
Such services are critical to ensuring features such as setting UEFI variables when installing the boot loader or updating UEFI variables. If they hang, then it's a UEFI issue. fwts cannot break out of the hang, because we are waiting for the processor to return back from the service, which it does not.
So:
1. It's not fwts fault if it blocks indefinitely.
2. In my opinion, the firmware is broken and not fit for purpose.
3. I cannot make fwts returned from a hung call like this; it really is impossible.
We need to escalate this to the BIOS experts in HWE for their opinion. But I am firmly declaring that any firmware that fails to execute such services is really unfit for use.