On Mon, 2 Dec 2024 22:56:25 -0800
wrote:
> 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've now had an apparent hang with this configuration, so it's an
in
On Tue, 2024-12-10 at 18:57 +0100, Uwe Kleine-König wrote:
> Hello,
Hi.
> On Tue, Dec 10, 2024 at 12:08:17PM +, Scott Ashcroft wrote:
> > Still happening with 6.12.3.
> > Pressing a number of keys (it doesn't need to be enter) will get
> > the
> > boot moving again.
>
> So it's not "Pressing
Hello,
On Tue, Dec 10, 2024 at 12:08:17PM +, Scott Ashcroft wrote:
> Still happening with 6.12.3.
> Pressing a number of keys (it doesn't need to be enter) will get the
> boot moving again.
So it's not "Pressing Enter makes the boot progress", but just pressing
(say) "A" for a few times helps
Still happening with 6.12.3.
Pressing a number of keys (it doesn't need to be enter) will get the
boot moving again.
Adding any sort of debug also seems to mask the issue.
I suspect it could be a change in systemd which triggered it.
Could it something needing more entropy in /dev/random which mash
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
On Fri, 22 Nov 2024 19:05:43 -0800
wrote:
> It now occurs to me that I may have installed a new version of
> udev/systemd (current "testing", v257~rc2-3) at the same time as
> kernel v6.11.7, so there may be some interaction there.
>
> The current situation on my system is that kernel v6.1 boots
On Fri, 22 Nov 2024 17:42:06 -0800
wrote:
> after this boot hang with kernel v6.11.7, the exact same thing happens
> with kernel v6.11.5, although this previously worked fine before the
> v6.11.7 boot failure.
>
> Fortunately, I still have kernel v6.1.0-26 installed (Debian package,
> as are the
I confirm this bug; same platform (AMD64), same kernel (6.11.7).
> The last line I see says how many files and blocks are ok.
This is also what I see -- fsck status (both clean) for root and /usr
filesystems (split on this system; current usrmerge package applied).
After that, nothing happens.
8 matches
Mail list logo
