Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #84689
| From | Chris Nospam <chris21k@gmx.de> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive) |
| Date | 2024-11-28 19:40 +0100 |
| Message-ID | <JNRAJ-ch4c-1@gated-at.bofh.it> (permalink) |
| References | <JJoxj-9jcI-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
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
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
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
csiph-web