FS#76718 - systemd-boot takes between 10 and 15 seconds to show the menu

Attached to Project: Arch Linux
Opened by Fred Morcos (fredmorcos) - Friday, 02 December 2022, 08:43 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 December 2022, 22:05 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When I boot up my PC (AMD), and my laptop (Intel), it now takes between 10 to 15 seconds (irregular) for systemd-boot to show the boot menu. This started happening recently (a few weeks ago) but I can't pinpoint exactly when. I'm happy to provide more information to debug this issue.

Additional info:
* package version(s)

systemd 252.2-2

* config and/or log files etc.

/boot/loader/loader.conf
default arch.conf
timeout 3

/boot/loader/entries/arch.conf
title Archlinux
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options rw add_efi_memmap mitigations=off nmi_watchdog=0 quiet nordrand ipv6.disable=1 bgrt_disable

* link to upstream bug report, if any

(I could not find anything upstream or on forums, etc)

Steps to reproduce:

Boot or reboot my machines.
   tree-boot-dir.txt (10 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 04 December 2022, 22:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 252.2-3
Comment by Fred Morcos (fredmorcos) - Friday, 02 December 2022, 08:45 GMT
Nothing really happens when waiting for the menu to show up, it's a blank screen on the Intel laptop, and the motherboard logo on the AMD desktop.

I tried different settings for `console-mode`, `auto-entries`, `auto-firmware` and `random-seed-mode` but nothing seems to have an effect.
Comment by Toolybird (Toolybird) - Friday, 02 December 2022, 21:33 GMT
Already known about upstream [1]. It appears a fix is available.

[1] https://github.com/systemd/systemd/issues/25510
Comment by Christian Hesse (eworm) - Friday, 02 December 2022, 21:56 GMT
Well, the fix [0] does not apply, as it depends on an earlier commit [1].

[0] https://github.com/systemd/systemd/commit/f6d59e2ebfc1bf50683a2e640aad501c372a50e4
[1] https://github.com/systemd/systemd/commit/8fec4f95be7a323410f9853b6773c810ba6c7152
Comment by Christian Hesse (eworm) - Friday, 02 December 2022, 22:05 GMT
Let's cherry-pick both... (Crossing fingers that nothing breaks.)
Can you test systemd-252.2-3, please?
Comment by Fred Morcos (fredmorcos) - Saturday, 03 December 2022, 13:25 GMT
systemd-252.2-3 works like a charm, thank you!

Loading...