** Changed in: broadcom-sta (Debian)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
T
** Changed in: plymouth (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
** Also affects: plymouth (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
T
Just to add more ubuntu/debian specific details because this includes a
kernel config options that was changed from vanilla kernel and that not
everyone may agree with and I had missed myself.
This seem to have started when crg_init was changed in the kernel to 1
to fix a CVE. This caused a change
This debian bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
discuss 4.15.0-54 the issue quite well, with the associated kernel
changes that brought the issues. Since I came across this bug first I
thought I would document this for others in the future. I came upon this
issue while ru
To add to Andrew's solution, in my case, the UUID in /etc/initramfs-
tools/config.d/resume was correct. But my swap was on an LVM partition.
I have found this blog post:
https://www.hiroom2.com/2018/05/01/ubuntu-1804-lvm-swap-wait-for-root-
en/
and changed the line in /etc/initramfs-tools/config.
Ive had this problem numerous times, and my solution works in all
situations.
When running dsmeg, the error shows up as:
[CODE]
[6.382044] random: crng init done
[6.382048] random: 7 urandom warning(s) missed due to ratelimiting
[ 32.162934] EXT4-fs (sda6): mounted filesystem with order
Neither rng-tools nor haveged solves this problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage not
Note that "random: crng init done" appearing very late is not a problem
by itself. User-noticeable delays only arise if some components (like
Bluetooth?) require the crng init to be completed in order for
themselves to initialize. This indicates poor design in those components
(they should never bl
... so using haveged is a workaround and not a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage notificat
Note that "random: crng init done" appearing very late is not a problem
by itself. User-noticeable delays only arise if some components (like
Bluetooth?) require the crng init to be completed in order for
themselves to initialize. This indicates poor design in those components
(they should never bl
** Changed in: broadcom-sta (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To m
Again Debian stretch with backports (kernel 4.18) on an Asus B53F with
another wireless card and without that broadcom-sta-dkms package.
Installing rng-tools solves the problem.
Apparently it also affects a Latitude E6410, but does not affect an
E4310 and an E5450 (none of them has broadcom-sta-dk
** Bug watch added: Debian Bug tracker #910504
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910504
** Also affects: broadcom-sta (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910504
Importance: Unknown
Status: Unknown
--
You received this bug notification be
Debian stretch with backports (kernels 4.17 and 4.18) on a Dell Latitude
E6420 with a Dell Wireless 1530 (Broadcom BCM43228) card.
This problem (although the delay is of about three minutes) has started
occurring on every boot after installing broadcom-sta-dkms (drivers for
the above wireless card
** Tags added: bionic
** Tags added: performance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage notificatio
Haveged and rng-tools5 or rng-tools didn't help me too.
I reported my problem to near topic
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1767782/comments/13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
haveged not solve for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage notifications about this bug go to:
At boot, the kernel waits for mouse movements to initialize the random number
generator.
Kernel messages on boot:
[code]
sudo dmesg | less
[/code]
The problem:
[code]
kernel: random: crng init done
[/code]
The solution:
[code]
sudo apt install haveged
sudo systemctl enable haveged
[/code]
--
Y
Since the last kernel update it is fixed form me.
$ uname -r
4.15.0-29-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng ini
In case it is helpful to anyone else, I found a resolution for my
specific case. This askubuntu question helped:
https://askubuntu.com/questions/1018907/ubuntu-installation-stuck-at-
random-crng-init-done . In sum: sudo apt install rng-tools
About 1 week ago, my Ubuntu 18.04 boot time went from ~1
First of all, I do not use Ubuntu, I use Debian, but I thought it would be a
nice input anyway, feel free to delete this if this don't help.
I had the same problem the first reboot I did after a system update to:
Linux version 4.9.0-6-amd64 (debian-ker...@lists.debian.org) (gcc
version 6.3.0 2017
For me this problem appeared after I upgraded from 17.10 to 18.04 two of
my machines. Both machines increased their boot times substantially (by
around 30 seconds).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Cheered too soon: after a few reboots the problem is back.
:(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage
I had the same problem (or a problem like the one at hand).
In posts #12 through #15 the user commenting out a line in hist /etc/cryptsetup
file resolved the problem.
As I did not have that file I installed the cryptsetup{,-bin} packages and
rebooted: problem resolved!
:D
--
You received this b
My etc/fstab looks like this:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
And here is a part of the gnome-system-log.
** Attachment added: "gnome-system-log_snippet_2018-01-06_13-35h.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+attachment/5032197/+files/gnome-system-log_snippet_2018-01-06_13-35h.txt
--
You received this bug notification becau
Ubuntu 16.04.3 - 64bit - Gnome
I can confirm the same bug - but my delay more like 8 minutes between
the login screen and the desktop showing up. My system is like that
since September 2017. I've reinstalled the kernel yesterday, which
didn't work.
Thomas_Do from ubuntuusers.de referred me to thi
You're welcome!
John Oberhauser <1685...@bugs.launchpad.net> schrieb am Mo., 8. Mai 2017,
21:31:
> I commented that line out. My boot is under 10 seconds now! Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/16
I commented that line out. My boot is under 10 seconds now! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
T
crypttab*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage notifications about this bug go to:
https://bugs.la
This is my cryptswap:
cryptswap1 UUID=31d32112-3452-744f-a8be-bf0648ace031 /dev/urandom
swap,offset=1024,cipher=aes-xts-plain64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot del
What does your /etc/crypttab look like?
John Oberhauser <1685...@bugs.launchpad.net> schrieb am Mo., 8. Mai 2017,
20:45:
> I'm having the same issue. Running Ubuntu Gnome on a Macbook Pro.
>
> Here is a snippet of my dmesg
>
> [4.102749] brcmfmac :03:00.0: Direct firmware load for
> brcm
I'm having the same issue. Running Ubuntu Gnome on a Macbook Pro.
Here is a snippet of my dmesg
[4.102749] brcmfmac :03:00.0: Direct firmware load for
brcm/brcmfmac43602-pcie.txt failed with error -2
[4.612866] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10
2015 06
I completely disabled swap now and it's working flawlessly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To manage n
I just checked my system and discovered configuration in my fstab and
crypttab that pointed to a nonexisted file. I created a swapfile and
corrected the configuration. Now my system boots in 13 seconds total!
Thanks for the hint!
As my system is a clean install, maybe there is a bug in the install
Typical - been looking at this off and on for a week or so, but posting
here got me looking again. Searched for "linux 90 second boot delay" and
found a few people who'd found that the swap partition was incorrectly
configured, causing a 90 second delay.
I'd also changed my SSD for a bigger one du
I've got a similar issue in that there's a pause of around 90 seconds
during boot, though the messages either side of the pause are different.
Thing is, there's no way of knowing whether the messages either side are
even relevant - I can't believe that an almost identical length pause is
not relate
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To
I just booted 4.11-rc8 as per your instructions and the issue is still
present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng ini
It's a fresh 17.04 installation no upgrade involved. I will try the latest
upstream kernel and report back.
Thanks for the hint!
Joseph Salisbury schrieb am Mo., 24. Apr.
2017, 19:41:
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notifica
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
Title:
Boot delayed for about 90 seconds until 'random: crng init done'
To
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
Output of: sudo lspci -vnvn > lspci-vnvn.log
** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+attachment/4867333/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
44 matches
Mail list logo
