Skip to contentSkip to conversation

x86_64 32-bit EFI mixed mode boot broken

DISCUSSION Clayton Craft 3 participants 18 messages Mar 21, 2024 – Apr 2, 2024

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

I've been chasing a problem with 32-bit EFI mixed mode booting on two different (x86_64) Intel Bay Trail platforms, where the system reboots or hangs seemingly very early somewhere before or after loading the kernel. I've not been able to get any output from the kernel or stub over efifb when the issue happens[0], and do not have serial console access on these systems.

v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able to boot OK on these platforms with mixed mode, and it looks like there are a lot of changes from 6.1..6.2 for EFI/mixed mode booting. I did managed to bisect the issue to:

commit e2ab9eab324cdf240de89741e4a1aa79919f0196
Author: Ard Biesheuvel <[email protected]>
Date: Tue Nov 22 17:10:02 2022 +0100

x86/boot/compressed: Move 32-bit entrypoint code into .text section

However I'm not sure how to proceed from here, or if my bisect is all that useful since the commit seems to be in the middle of a bunch of changes I do not understand. I've been using systemd-boot to test this (both the full bootloader and UKI w/ the sd-boot stub). Is 32-bit mixed mode on x86_64 working for others?

Thanks,
Clayton

0. Using "debug ignore_loglevel earlycon=efifb earlyprintk=efi,keep efi=debug"

maintainer
#1 lore raw

(cc Hans)

Quoted 10 lines · Clayton Craft

I've been chasing a problem with 32-bit EFI mixed mode booting on two different (x86_64) Intel Bay Trail platforms, where the system reboots or hangs seemingly very early somewhere before or after loading the kernel. I've not been able to get any output from the kernel or stub over efifb when the issue happens[0], and do not have serial console access on these systems.

v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able to boot OK on these platforms with mixed mode, and it looks like there are a lot of changes from 6.1..6.2 for EFI/mixed mode booting.

v6.1 just received some EFI related backports, so please check the latest v6.1.y as well.

Quoted 7 lines

I did managed to bisect the
issue to:

commit e2ab9eab324cdf240de89741e4a1aa79919f0196
Author: Ard Biesheuvel <[email protected]>
Date: Tue Nov 22 17:10:02 2022 +0100

Quoted 7 lines

x86/boot/compressed: Move 32-bit entrypoint code into .text section

However I'm not sure how to proceed from here, or if my bisect is all that useful since the commit seems to be in the middle of a bunch of changes I do not understand. I've been using systemd-boot to test this (both the full bootloader and UKI w/ the sd-boot stub). Is 32-bit mixed mode on x86_64 working for others?

I usually test on 32-bit OVMF built with LOAD_X64_ON_IA32_ENABLE, which allows the use of the compat entry point. This is different from the EFI handover protocol, and I am not sure which one you are using.

I have never had any reports, or noticed any issues myself. Last time I tried (some weeks ago) it was working for me.
CC'ing Hans who may have more data points.

#2 lore raw
Quoted 6 lines · On Thu, 21 Mar 2024 23:48:09 +0100 Ard Biesheuvel <[email protected]> wrote:
Quoted 3 lines

v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able to boot OK on these platforms with mixed mode, and it looks like there are a lot of changes from 6.1..6.2 for EFI/mixed mode booting.

v6.1 just received some EFI related backports, so please check the latest v6.1.y as well.

I just gave v6.1.82 a try, and it fails to boot for me. That seems to be a regression from the 6.1.0 that I tested previously.

Quoted 3 lines

I usually test on 32-bit OVMF built with LOAD_X64_ON_IA32_ENABLE, which allows the use of the compat entry point. This is different from the EFI handover protocol, and I am not sure which one you are using.

I should have mentioned this previously, here's the EFI-related kconfig that I am using. If there's anything missing then please let me know:

CONFIG_EFI=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_ESRT=y
# CONFIG_EFI_HANDOVER_PROTOCOL is not set
CONFIG_EFI_MIXED=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_STUB=y
CONFIG_EFI_VARS_PSTORE=m
CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y

Note that the EFI handover protocol support is disabled, I was under the impression that it's not required for mixed mode.

Please let me know if there's any more information I can provide about my testing / setup.

-Clayton

maintainer
#3 lore raw
Quoted 29 lines · Clayton Craft
Quoted 6 lines · On Thu, 21 Mar 2024 23:48:09 +0100 Ard Biesheuvel <[email protected]> wrote:
Quoted 3 lines

v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able to boot OK on these platforms with mixed mode, and it looks like there are a lot of changes from 6.1..6.2 for EFI/mixed mode booting.

v6.1 just received some EFI related backports, so please check the latest v6.1.y as well.

I just gave v6.1.82 a try, and it fails to boot for me. That seems to be a regression from the 6.1.0 that I tested previously.

Quoted 3 lines

I usually test on 32-bit OVMF built with LOAD_X64_ON_IA32_ENABLE, which allows the use of the compat entry point. This is different from the EFI handover protocol, and I am not sure which one you are using.

I should have mentioned this previously, here's the EFI-related kconfig that I am using. If there's anything missing then please let me know:

CONFIG_EFI=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_ESRT=y
# CONFIG_EFI_HANDOVER_PROTOCOL is not set
CONFIG_EFI_MIXED=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_STUB=y
CONFIG_EFI_VARS_PSTORE=m
CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y

Quoted 3 lines

Note that the EFI handover protocol support is disabled, I was under the impression that it's not required for mixed mode.

That depends on the bootloader. One of the changes around that time is the introduction of this Kconfig symbol: before that, the EFI handover protocol was always supported but now it can be compiled out. So the safe choice is to enable it.

However, while looking more deeply into this, I noticed that we are running quite low own stack space. Mixed mode is different because it calls into the boot services using the decompressor's boot stack, rather than using the one that was provided by firmware at entry. (Note that the UEFI spec mandates 128k of stack space)

In my case, I bisected the regression to

commit 5c4feadb0011983bbc4587bc61056c7b379d9969 (HEAD)

Author: Ard Biesheuvel <[email protected]>
Date:   Mon Aug 7 18:27:16 2023 +0200

x86/decompressor: Move global symbol references to C code

which moves the boot stack into a different memory region. Formerly, we'd end up at the far end of the heap when overrunning the stack but now, we end up crashing. Of course, overwriting the heap can cause problems of its own, so we'll need to bump this in any case.

Could you give this a try please?

arch/x86/include/asm/boot.h +1 -1
@@ -38,7 +38,7 @@
 #endif
 
 #ifdef CONFIG_X86_64
-# define BOOT_STACK_SIZE       0x4000
+# define BOOT_STACK_SIZE       0x10000
 
 /*
  * Used by decompressor's startup_32() to allocate page tables for identity
#4 lore raw
Quoted 4 lines · On Fri, 22 Mar 2024 13:52:05 +0100 Ard Biesheuvel <[email protected]> wrote:

That depends on the bootloader. One of the changes around that time is the introduction of this Kconfig symbol: before that, the EFI handover protocol was always supported but now it can be compiled out. So the safe choice is to enable it.

I am using systemd-boot, and based on my understanding of its source it seems to only use handover on old kernels that don't support LINUX_INITRD_MEDIA_GUID.

Quoted 26 lines

However, while looking more deeply into this, I noticed that we are running quite low own stack space. Mixed mode is different because it calls into the boot services using the decompressor's boot stack, rather than using the one that was provided by firmware at entry. (Note that the UEFI spec mandates 128k of stack space)

In my case, I bisected the regression to

commit 5c4feadb0011983bbc4587bc61056c7b379d9969 (HEAD)

Author: Ard Biesheuvel <[email protected]>
Date:   Mon Aug 7 18:27:16 2023 +0200

x86/decompressor: Move global symbol references to C code

which moves the boot stack into a different memory region. Formerly, we'd end up at the far end of the heap when overrunning the stack but now, we end up crashing. Of course, overwriting the heap can cause problems of its own, so we'll need to bump this in any case.

Could you give this a try please?

arch/x86/include/asm/boot.h line 44

Quoted 8 lines
arch/x86/include/asm/boot.h +1 -1
@@ -38,7 +38,7 @@
 #endif
 
 #ifdef CONFIG_X86_64
-# define BOOT_STACK_SIZE       0x4000
+# define BOOT_STACK_SIZE       0x10000
 
 /*
  * Used by decompressor's startup_32() to allocate page tables for identity

Just gave this a try, on 6.1.82, and the system still reboots after selecting the kernel in the bootloader. So it seems like my problem is different.

As I mentioned initially, I bisected my failure to e2ab9eab32. Does that give any hint about what might be the problem?

-Clayton

maintainer
#5 lore raw
Quoted 9 lines · Clayton Craft
Quoted 4 lines · On Fri, 22 Mar 2024 13:52:05 +0100 Ard Biesheuvel <[email protected]> wrote:

That depends on the bootloader. One of the changes around that time is the introduction of this Kconfig symbol: before that, the EFI handover protocol was always supported but now it can be compiled out. So the safe choice is to enable it.

I am using systemd-boot, and based on my understanding of its source it seems to only use handover on old kernels that don't support LINUX_INITRD_MEDIA_GUID.

That does ring a bell. So that means you must be using the .compat entry point, which is what 32-bit OVMF uses too.

Quoted 32 lines
Quoted 32 lines

However, while looking more deeply into this, I noticed that we are running quite low own stack space. Mixed mode is different because it calls into the boot services using the decompressor's boot stack, rather than using the one that was provided by firmware at entry. (Note that the UEFI spec mandates 128k of stack space)

In my case, I bisected the regression to

commit 5c4feadb0011983bbc4587bc61056c7b379d9969 (HEAD)

Author: Ard Biesheuvel <[email protected]>
Date:   Mon Aug 7 18:27:16 2023 +0200

x86/decompressor: Move global symbol references to C code

which moves the boot stack into a different memory region. Formerly, we'd end up at the far end of the heap when overrunning the stack but now, we end up crashing. Of course, overwriting the heap can cause problems of its own, so we'll need to bump this in any case.

Could you give this a try please?

arch/x86/include/asm/boot.h +1 -1
@@ -38,7 +38,7 @@
 #endif
 
 #ifdef CONFIG_X86_64
-# define BOOT_STACK_SIZE       0x4000
+# define BOOT_STACK_SIZE       0x10000
 
Quoted 6 lines

arch/x86/include/asm/boot.h line 44

Quoted 2 lines
arch/x86/include/asm/boot.h +0 -0
 /*
  * Used by decompressor's startup_32() to allocate page tables for identity

Just gave this a try, on 6.1.82, and the system still reboots after selecting the kernel in the bootloader. So it seems like my problem is different.

Yeah, it was a long shot.

Quoted 3 lines

As I mentioned initially, I bisected my failure to e2ab9eab32. Does that give any hint about what might be the problem?

Not at all, unfortunately. What we might try is to back out the changes step by step. I can prepare a branch for you if you like.

#6 lore raw
Quoted 8 lines · Ard Biesheuvel
Quoted 4 lines

As I mentioned initially, I bisected my failure to e2ab9eab32. Does that give

any hint about what might be the problem?

Not at all, unfortunately. What we might try is to back out the

changes step by step. I can prepare a branch for you if you like.

Yeah sure, if you don't mind! I'd be happy to test changes in a branch to try and figure out what is causing this.

-Clayton

maintainer
#7 lore raw
Quoted 9 lines · Clayton Craft
Quoted 5 lines · Ard Biesheuvel
Quoted 4 lines

As I mentioned initially, I bisected my failure to e2ab9eab32. Does that give

any hint about what might be the problem?

Quoted 7 lines
Quoted 3 lines

Not at all, unfortunately. What we might try is to back out the

changes step by step. I can prepare a branch for you if you like.

Yeah sure, if you don't mind! I'd be happy to test changes in a branch to try and figure out what is causing this.

I have pushed a branch below that reverts the patch you identified in 4 separate steps. Could you please check which step makes your system boot again?

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton

#8 lore raw
Quoted 11 lines · Ard Biesheuvel

On Fri, 22 Mar 2024 at 19:57, Clayton Craft <[email protected]> wrote:

I have pushed a branch below that reverts the patch you identified in

4 separate steps. Could you please check which step makes your system

boot again?

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton

Thanks a lot for doing this, I really appreciate the help!

It looks like if I build from 868a7245, booting breaks again on my Bay Trail systems. If I put back 00e85ab5, they boot again.

-Clayton

maintainer
#9 lore raw
Quoted 11 lines · Clayton Craft
Quoted 7 lines · Ard Biesheuvel

On Fri, 22 Mar 2024 at 19:57, Clayton Craft <[email protected]> wrote:

I have pushed a branch below that reverts the patch you identified in

4 separate steps. Could you please check which step makes your system

Quoted 9 lines
Quoted 4 lines

boot again?

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton

Thanks a lot for doing this, I really appreciate the help!

It looks like if I build from 868a7245, booting breaks again on my Bay Trail systems. If I put back 00e85ab5, they boot again.

OK.

I have reshuffled the branch and put the patch you identified as the one fixing the boot first. Please double check whether this change still fixes the boot for you.

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-2

If so, we can try applying it to mainline, and merge it if it works there too.

If not, we will need better debugging to figure out what the hell is going on.

maintainer
#10 lore raw
Quoted 25 lines · Ard Biesheuvel
Quoted 11 lines · Clayton Craft
Quoted 7 lines · Ard Biesheuvel

On Fri, 22 Mar 2024 at 19:57, Clayton Craft <[email protected]> wrote:

I have pushed a branch below that reverts the patch you identified in

4 separate steps. Could you please check which step makes your system

Quoted 9 lines
Quoted 4 lines

boot again?

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton

Thanks a lot for doing this, I really appreciate the help!

It looks like if I build from 868a7245, booting breaks again on my Bay Trail systems. If I put back 00e85ab5, they boot again.

OK.

Quoted 8 lines

I have reshuffled the branch and put the patch you identified as the one fixing the boot first. Please double check whether this change still fixes the boot for you.

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-2

If so, we can try applying it to mainline, and merge it if it works there too.

I have a mainline branch with the same change applied, please try that one too.

#11 lore raw
Quoted 6 lines · Ard Biesheuvel
Quoted 5 lines · Ard Biesheuvel

OK.

I have reshuffled the branch and put the patch you identified as the

Quoted 7 lines
Quoted 7 lines

one fixing the boot first. Please double check whether this change

still fixes the boot for you.

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-2

If so, we can try applying it to mainline, and merge it if it works there too.

This branch boots on my Bay Trail systems.

Quoted 1 line

I have a mainline branch with the same change applied, please try that one too.

I assume this is the efi-mixed-mode-boot-hack branch, if so then this branch also boots on these systems.

-Clayton

#12 lore raw
In reply to Ard Biesheuvel

Hi,

Quoted 32 lines · Ard Biesheuvel

(cc Hans)

Quoted 10 lines · Clayton Craft

I've been chasing a problem with 32-bit EFI mixed mode booting on two different (x86_64) Intel Bay Trail platforms, where the system reboots or hangs seemingly very early somewhere before or after loading the kernel. I've not been able to get any output from the kernel or stub over efifb when the issue happens[0], and do not have serial console access on these systems.

v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able to boot OK on these platforms with mixed mode, and it looks like there are a lot of changes from 6.1..6.2 for EFI/mixed mode booting.

v6.1 just received some EFI related backports, so please check the latest v6.1.y as well.

Quoted 7 lines

I did managed to bisect the
issue to:

commit e2ab9eab324cdf240de89741e4a1aa79919f0196
Author: Ard Biesheuvel <[email protected]>
Date: Tue Nov 22 17:10:02 2022 +0100

Quoted 7 lines

x86/boot/compressed: Move 32-bit entrypoint code into .text section

However I'm not sure how to proceed from here, or if my bisect is all that useful since the commit seems to be in the middle of a bunch of changes I do not understand. I've been using systemd-boot to test this (both the full bootloader and UKI w/ the sd-boot stub). Is 32-bit mixed mode on x86_64 working for others?

Quoted 7 lines

I usually test on 32-bit OVMF built with LOAD_X64_ON_IA32_ENABLE, which allows the use of the compat entry point. This is different from the EFI handover protocol, and I am not sure which one you are using.

I have never had any reports, or noticed any issues myself. Last time I tried (some weeks ago) it was working for me.
CC'ing Hans who may have more data points.

I've been offline for most of the week and I see that in the mean time you seem to have found a fix, great.

FWIW I have been booting everything up to 6.8.0 on my own mixed-mode Bay Trail tablets without issues, so the problem seems to be specific to certain BIOS-es.

Please Cc me on the final fix, then I can test that early and double check that things don't regress on other mixed-mode Bay Trail devices.

Regards,

Hans

maintainer
#13 lore raw
Quoted 47 lines · Hans de Goede

Hi,

Quoted 32 lines · Ard Biesheuvel

(cc Hans)

Quoted 10 lines · Clayton Craft

I've been chasing a problem with 32-bit EFI mixed mode booting on two different (x86_64) Intel Bay Trail platforms, where the system reboots or hangs seemingly very early somewhere before or after loading the kernel. I've not been able to get any output from the kernel or stub over efifb when the issue happens[0], and do not have serial console access on these systems.

v6.8 fails for me, and presumably so does everything back to v6.2. v6.1 is able to boot OK on these platforms with mixed mode, and it looks like there are a lot of changes from 6.1..6.2 for EFI/mixed mode booting.

v6.1 just received some EFI related backports, so please check the latest v6.1.y as well.

Quoted 7 lines

I did managed to bisect the
issue to:

commit e2ab9eab324cdf240de89741e4a1aa79919f0196
Author: Ard Biesheuvel <[email protected]>
Date: Tue Nov 22 17:10:02 2022 +0100

Quoted 7 lines

x86/boot/compressed: Move 32-bit entrypoint code into .text section

However I'm not sure how to proceed from here, or if my bisect is all that useful since the commit seems to be in the middle of a bunch of changes I do not understand. I've been using systemd-boot to test this (both the full bootloader and UKI w/ the sd-boot stub). Is 32-bit mixed mode on x86_64 working for others?

Quoted 7 lines

I usually test on 32-bit OVMF built with LOAD_X64_ON_IA32_ENABLE, which allows the use of the compat entry point. This is different from the EFI handover protocol, and I am not sure which one you are using.

I have never had any reports, or noticed any issues myself. Last time I tried (some weeks ago) it was working for me.
CC'ing Hans who may have more data points.

I've been offline for most of the week and I see that in the mean time you seem to have found a fix, great.

Quoted 7 lines

FWIW I have been booting everything up to 6.8.0 on my own mixed-mode Bay Trail tablets without issues, so the problem seems to be specific to certain BIOS-es.

Please Cc me on the final fix, then I can test that early and double check that things don't regress on other mixed-mode Bay Trail devices.

Thanks.

I pushed another branch

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-3

which has a proper fix for the issue that you found.

As it turns out, the compat mixed mode (with handover protocol) was broken from the beginning, and the change you identified just happened to trigger it on your hardware.

author Tested-by
#14 lore raw
Quoted 6 lines · Ard Biesheuvel

Thanks.

I pushed another branch

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-3

Quoted 7 lines

which has a proper fix for the issue that you found.

As it turns out, the compat mixed mode (with handover protocol) was

broken from the beginning, and the change you identified just happened

to trigger it on your hardware.

Tested and fixes booting on my Bay Trail tablet and NUC. Thanks for fixing this!

-Clayton

maintainer
#15 lore raw
Quoted 14 lines · Clayton Craft
Quoted 10 lines · Ard Biesheuvel

Thanks.

I pushed another branch

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-3

which has a proper fix for the issue that you found.

As it turns out, the compat mixed mode (with handover protocol) was

Quoted 9 lines
Quoted 3 lines

broken from the beginning, and the change you identified just happened

to trigger it on your hardware.

Tested and fixes booting on my Bay Trail tablet and NUC. Thanks for fixing this!

Thanks!

#16 lore raw
Quoted 10 lines · On Sun, 24 Mar 2024 22:53:47 +0200 Ard Biesheuvel <[email protected]> wrote:
Quoted 10 lines
Quoted 10 lines

Thanks.

I pushed another branch

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-3

which has a proper fix for the issue that you found.

As it turns out, the compat mixed mode (with handover protocol) was

Quoted 8 lines
Quoted 8 lines
Quoted 3 lines

broken from the beginning, and the change you identified just happened

to trigger it on your hardware.

Tested and fixes booting on my Bay Trail tablet and NUC. Thanks for fixing this!

So... maybe my testing wasn't as thorough as I thought, OR I am experiencing an unrelated problem. In any case, I'm having some difficulty figuring out what to blame. When using this patch on the 6.6 LTS:

1) kernel seems to panic right after displaying disabling bootcon [efifb0]. I determined that it's panicking by setting panic=-1 and seeing it reboot after showing that message. I can work around it by setting keep_bootcon, but that's not ideal.

2) kernel complains about no root (from initrd). I can work around this by passing initrd=my-initramfs on the kernel cmdline.

I haven't tried any newer kernels yet. The second issue above makes me wonder if your patch related to args might be to blame, but I'm not sure. Any help poking around further would be greatly appreciated :)

-Clayton

maintainer
#17 lore raw
Quoted 21 lines · Clayton Craft
Quoted 10 lines · On Sun, 24 Mar 2024 22:53:47 +0200 Ard Biesheuvel <[email protected]> wrote:
Quoted 10 lines
Quoted 10 lines

Thanks.

I pushed another branch

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-clayton-3

which has a proper fix for the issue that you found.

As it turns out, the compat mixed mode (with handover protocol) was

Quoted 8 lines
Quoted 8 lines
Quoted 3 lines

broken from the beginning, and the change you identified just happened

to trigger it on your hardware.

Tested and fixes booting on my Bay Trail tablet and NUC. Thanks for fixing this!

Quoted 9 lines

So... maybe my testing wasn't as thorough as I thought, OR I am experiencing an unrelated problem. In any case, I'm having some difficulty figuring out what to blame. When using this patch on the 6.6 LTS:

1) kernel seems to panic right after displaying disabling bootcon [efifb0]. I determined that it's panicking by setting panic=-1 and seeing it reboot after showing that message. I can work around it by setting keep_bootcon, but that's not ideal.

First of all, if you make it all the way to this point, it is unlikely that this is the same issue. The issue that was fixed was preventing the boot from proceeding past the very early 32-bit boot stage in the decompressor, and by the time you hit this panic, the kernel is up an running.

Quoted 3 lines

2) kernel complains about no root (from initrd). I can work around this by passing initrd=my-initramfs on the kernel cmdline.

So why is systemd-boot not passing this directly? AFAIK this is the default method for systemd-boot, and I don't think it implements any other methods.

Quoted 4 lines

I haven't tried any newer kernels yet. The second issue above makes me wonder if your patch related to args might be to blame, but I'm not sure. Any help poking around further would be greatly appreciated :)

You might try this stable -rc

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=linux-6.6.y

which should get released any day now. It has a couple of EFI related fixes, although none of them seem related in particular.

Another thing you might try is to pass efi=noruntime to the boot, to check whether EFI is implicated in this to begin with.