composefs: Type 1 kernel path on the ESP is too long for HP G10 firmware, boot hangs

Aperta
#2,585 8 commenti 4 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
49/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, rust

Direzione di ricerca

Start by tracing how the composefs backend creates the Type 1 kernel directory and loader entry; the issue does not name source files or tests. The evidence points to the ESP path length as the cause: shortening the directory lets the same kernel boot on affected HP G10 firmware. Done means choosing and implementing a path that avoids the reported hang, then validating it on the affected hardware.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What happened?

On several HP G10 business laptops, firmware hangs (black screen, hard lock) when systemd-boot loads the kernel from the Type 1 directory that the composefs backend writes to the ESP. Every stock install produces a path like this:

/EFI/Linux/bootc_composefs-<128 hex verity>/vmlinuz

That is 163 characters. Reporters in projectbluefin/dakota#1648 bisected the limit by truncating the directory name by hand: a 160 character kernel path boots, 163 hangs. The kernel, initrd and kernel arguments were unchanged, only the directory was renamed.

Affected so far:

  • HP EliteBook 845 G10 (AMD, BIOS V82)
  • HP EliteBook 840 G10 (Intel graphics)
  • HP ZBook Firefly 14 G10 A

We ship Dakota with --composefs-backend and systemd-boot by default, which is probably why this has not shown up elsewhere.

Loader entries

Original entry generated by bootc (hangs):

title Bluefin
version 20260921
linux /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e050/vmlinuz
initrd /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e050/initrd
options root=LABEL=root rw composefs=023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e050 <image kargs> rd.luks.name=<uuid>=root
sort-key bootc-bluefin-dakota-0

Longest entry that boots, with the last three hex characters of the directory removed (160 characters):

linux /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e/vmlinuz
initrd /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e/initrd

A fully short directory (/EFI/Linux/bootc_composefs-dakota/) also boots.

I don't have one of these machines myself, but I can build a Dakota image with a candidate fix and ask the reporters in #1648 to verify it on the affected hardware.

Versions
  • bootc v1.17.1
  • systemd-boot, Type 1 BLS entries, composefs backend
  • Image: ghcr.io/projectbluefin/dakota:stable
Lingua principale
Rust
Stelle
2.3k
Fork
230
Merge medio
2g 11h
PR unite (30g)
42

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bootc-dev/bootc

Tutte le issue di bootc-dev/bootc

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.