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

Aberta
#2,585 8 comentários 4 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
49/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
linux, rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
Rust
Estrelas
2.3k
Forks
230
Merge médio
2d 11h
PRs com merge (30d)
42

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de bootc-dev/bootc

Todas as issues de bootc-dev/bootc

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.