Your message dated Thu, 20 Feb 2025 12:16:19 +0100 (CET)
with message-id <20250220111619.d340abe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #910765,
regarding very slow boot with backport kernel (+workaround)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
910765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.18.0-0.bpo.1-amd64


Debian stable (updated) with kernel 4.18.0-0.bpo.1-amd64 #1 SMP Debian
4.18.6-1~bpo9+1 (2018-09-13) x86_64 GNU/Linux

updating from standard kernel to backports, the boot is very slow (gdm
login appears after ~3 minutes)

boot process is stuck before "crng init done" as you can see by messages:
Oct 10 18:06:24 gozzi-MBP NetworkManager[598]: <info>  [1539187584.4027]
dhcp6 (wlp4s0b1): state changed bound -> done
Oct 10 18:09:15 gozzi-MBP kernel: [  194.178094] random: crn

Workaround that solves the problem: install the package haveged


workaround tried but not working
install backport headers
install rng-tools

hardware informations
Manufacturer: Apple Inc.
    Product Name: Mac-C3EC7CD22292981F
    Version: MacBookPro10,1

thanks for the effort
stefano

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---

Reply via email to