Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #84689 > unrolled thread

Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive)

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive) Chris Nospam <chris21k@gmx.de> - 2024-11-28 19:40 +0100
    Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive) Salvatore Bonaccorso <carnil@debian.org> - 2024-11-30 14:20 +0100

#84689 — Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive)

Dear Salvatore,

that seems to be a wired thing!?

No matter of temporarily within grub bootmenu e and F10 or permanently by changing /etc/default/grub and update-grub, as soon I replace kernel parameter  quit  by  -- systemd.log_level=debug  the system boots successfully on ever trie. I did more than 25 boots (warm and cold) and every single one was successfull then. On the first boot after restoring the default boot parameters and booting, the system has run into the hang situation again :(

Also in some few cases where I only did remove  quit  (and not adding  -- systemd.log_level=debug ), this suffices for correct booting. Can this be by coincidence, or timing behaviour/race conditions?

Chris

[toc] | [next] | [standalone]

#84706

Hi Chris,

On Thu, Nov 28, 2024 at 06:32:17PM +0000, Chris Nospam wrote:
> Dear Salvatore,
> 
> that seems to be a wired thing!?
> 
> No matter of temporarily within grub bootmenu e and F10 or
> permanently by changing /etc/default/grub and update-grub, as soon I
> replace kernel parameter  quit  by  -- systemd.log_level=debug  the
> system boots successfully on ever trie. I did more than 25 boots
> (warm and cold) and every single one was successfull then. On the
> first boot after restoring the default boot parameters and booting,
> the system has run into the hang situation again :(
> 
> Also in some few cases where I only did remove  quit  (and not
> adding  -- systemd.log_level=debug ), this suffices for correct
> booting. Can this be by coincidence, or timing behaviour/race
> conditions?

Thanks for doing those tests. I'm still unable to reproduce the issue
on own setups so far.

Would you still as well be able to configure a netconsole so we see if
we get more information of it, or does it influece the timings as well
enough already that you get sucessful boots?

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web