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

Ouverte
#2,585 8 commentaires 4 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
1-2 jours
Accessibilité débutants
49/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
linux, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Rust
Étoiles
2.3k
Forks
230
Merge moyen
2 j 11 h
PR mergées (30 j)
42

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de bootc-dev/bootc

Toutes les issues de bootc-dev/bootc

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.