Bug#1087616: confirm linux-image-6.11.7-amd64 boot failure

To: 1087616@bugs.debian.org
Subject: Bug#1087616: confirm linux-image-6.11.7-amd64 boot failure
From: Chris Nospam <chris21k@gmx.de>
Date: Tue, 3 Dec 2024 14:50:34 +0000
Message-id: <[🔎] trinity-c56dd49d-f6a5-4c03-9b30-d3cf02859024-1733237434802@trinity-msg-rest-gmx-gmx-live-548599f845-x7jfc>
Reply-to: Chris Nospam <chris21k@gmx.de>, 1087616@bugs.debian.org
References: <173175367577.3660.3066924976380935123.reportbug@debian>

ian_bruce@mail.ru wrote at Mon, 2 Dec 2024 22:56:25 -0800
&gt; However, having now installed systemd v257~rc3-1, the problem seems to
&gt; have gone away, without altering the boot parameters. This is the case
&gt; at least with kernel linux-image-6.11.10-amd64.

I cannot confirm that. The hang in with systemd v257-rc3-1 and kernel 6.11.10-1 is definitly still present on my physical and virtual systems. However, it seems to occur slightly not so often as before, but that may be misleading.
However, I am quite happy that someone can reproduce, that it mainly (always?) occurs with (solely?) kernel parameter  quiet  set.

Chris

Reply to:

Prev by Date: Bug#1087940: marked as done (linux-image-6.11.4-amd64: Bluetooth (Bluez) stops working with some peripherials with kernels after linux-image-6.11.2)
Next by Date: Re: Re: Bug#1088739: colors make ip's output unreadable
Previous by thread: Bug#1087616: confirm linux-image-6.11.7-amd64 boot failure
Next by thread: Bug#1087616: confirm linux-image-6.11.7-amd64 boot failure
Index(es):
- Date
- Thread