Debian boot failure with UEFI runtime variables enabled

Heinrich Schuchardt xypron.glpk at gmx.de
Thu Jul 23 17:13:44 CEST 2020


On 23.07.20 17:07, Grant Likely wrote:
> On Thu, Jul 23, 2020 at 3:40 PM Heinrich Schuchardt <xypron.glpk at gmx.de> wrote:
>>
>> On 23.07.20 14:23, Grant Likely wrote:
>>> Hi Heinrich,
>>>
>>> I've run into a problem with mainline U-Boot. Debian unstable (distro
>>> kernel) fails to boot after commit b02a707152, "efi_loader: enable
>>> UEFI variables at runtime". Kernel boots fine before that commit. Boot
>>> log is attached. Looks like it is failing in a workqueue that is
>>> calling runtime services; but I haven't dug in yet.
>>>
>>> I'm not doing anything exotic with this build. Mainline U-Boot,
>>> mainline TFA, and booting the kernel with an up-to-date dtb.
>>>
>>> g.
>>
>> Hello Grant,
>>
>> this is the patch you are needing:
>>
>> https://lists.denx.de/pipermail/u-boot/2020-July/421193.html
>> [PATCH 1/1] efi_loader: efi_current_var after SetVirtualAddressMap
>
> Got it. Working now. Thanks!
> g.
>

There is also an issue to current Linux kernels fixed by:

efi/efivars: Expose RT service availability via efivars abstraction

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=f88814cc2578c121e6edef686365036db72af0ed

Without the patch if SetVariable() is not available, you cannot access
GetVariable() in Linux.

Best regards

Heinrich


More information about the U-Boot mailing list