ian_br...@mail.ru wrote at Mon, 2 Dec 2024 22:56:25 -0800
> However, having now installed systemd v257~rc3-1, the problem seems to
> have gone away, without altering the boot parameters. This is the case
> at least with kernel linux-image-6.11.10-amd64.
I cannot confirm that. The hang in with syst
Dear Salvatore,
now up to date with testing's kernel 6.11.10-1 and systemd 257rc3-1, the same
issue. In that config I saw the hang even once with my kvm virtualized system.
> Would you still as well be able to configure a netconsole so we see if
> we get more information of it
Of course, howeve
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 mor
I also can confirm that booting is not possible in testing any more: Kernel
6.11.9 and 6.11.7 and systemd v257~rc2-3 in a standard grub/efi/ext setup
without cryptofs or similar on a sata ssd (so probably better to change the
title of the thread). This happens since the upgrade which (among othe
Meanwhile my Debian Testing systems have (per default) upgraded to libbsd
0.9.1 (and kernel 4.16.0-2). Unfortunaetly, this does not fix the problem
(long ssdm start) under virtualization by kvm, although according to #898088
libvirt 0.9.0-1 should have alredy fixed this.
On productive bare metal I
5 matches
Mail list logo
