[Buildroot] [git commit] board/qemu/x86_64-efi/linux.config: enable CONFIG_EFI_STUB to fix with grub2 >= 2.14

Peter Korsgaard <[email protected]>
Newsgroups net.busybox.buildroot
Message-ID <[email protected]>
commit: https://gitlab.com/buildroot.org/buildroot/-/commit/ca2c31b019eadbed5875dce52ed8e6249a606e86
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master

Since Buildroot commit [1] (boot/grub2: bump to version 2.14), the
qemu_x86_64_efi_defconfig fails at boot time with the error:

    !!!! X64 Exception Type - 0E(#PF - Page-Fault)  CPU Apic ID - 00000000 !!!!
    ExceptionData - 0000000000000003  I:0 R:0 U:0 W:1 P:1 PK:0 SS:0 SGX:0

This issue happens because EDK2 and Grub 2.14 are enabling NX and the
kernel lacks the CONFIG_EFI_STUB configuration. For the full explanation
see the commit log of [2] (board/pc/linux.config: enable CONFIG_EFI_STUB).

This commit enables CONFIG_EFI_STUB=y.

Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/15969219375

[1] https://gitlab.com/buildroot.org/buildroot/-/commit/da278ba1dab7e29369879c8a29cbd1b42dbe9ce0
[2] https://gitlab.com/buildroot.org/buildroot/-/commit/1c1fa6ce67448ef8bab16d795623be730ff658ea

Reported-by: Romain Naour <[email protected]>
Signed-off-by: Julien Olivain <[email protected]>
Signed-off-by: Peter Korsgaard <[email protected]>
---
 board/qemu/x86_64-efi/linux.config | 1 +
 1 file changed, 1 insertion(+)

diff --git a/board/qemu/x86_64-efi/linux.config b/board/qemu/x86_64-efi/linux.config
index 9362b7ecb5..4f5f0b386d 100644
--- a/board/qemu/x86_64-efi/linux.config
+++ b/board/qemu/x86_64-efi/linux.config
@@ -3,6 +3,7 @@ CONFIG_SMP=y
 CONFIG_HYPERVISOR_GUEST=y
 CONFIG_PARAVIRT=y
 CONFIG_EFI=y
+CONFIG_EFI_STUB=y
 # CONFIG_GCC_PLUGINS is not set
 CONFIG_MODULES=y
 CONFIG_MODULE_UNLOAD=y
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.