Skip to content

crng.init blocks boot process without a mouse. #2799

@rin67630

Description

@rin67630

Is this the right place for my bug report?
I believe that crng.init belongs to the kernel.
It is supposed to provide some entropy to the random generator from the mouse events.
The Raspberry Pi is frequently used headless e.g. over VNC.

Describe the bug
VNC does not start until a mouse is plugged in.

To reproduce
The behaviour does not happen with a pristine install of 2018-11-13-raspbian-stretch, but has been frequently reported, also with previous versions of Raspbian, on all Raspberry Pi models.

Expected behaviour
The boot process should perform smoothly also without a mouse plugged in.

Actual behaviour
During boot the system hangs after the initialisation of fuse: (etc/logs/messages)
Jan 8 16:12:50 Stretch11 kernel: [ 316.155022] random: crng init done
Jan 8 16:12:50 Stretch11 kernel: [ 316.155036] random: 7 urandom warning(s) missed due to ratelimiting

It can stay at that stage several minutes or forever. As soon as you plug a mouse, it continues.

System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:

  • Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
    Bug found on many current models incuding Pi3B+, Pi3A+, PiZeroW
  • Which OS and version (cat /etc/rpi-issue)?
    Raspberry Pi reference 2018-11-13, but also on previous versions.
  • Which firmware version (vcgencmd version)?
    Nov 4 2018 16:31:07, but also on previous versions.
  • Which kernel version (uname -a)?
    Linux Stretch11.2018-3APlus 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
    Logs
    If applicable, add the relevant output from dmesg or similar.
    See Additional context.
    Additional context
    Does not happen on very pristine installs, needs additional software installed (did not yet find which one), but has been frequently reported.
    Does NEVER happen with a mouse connected. Boot process resumes as soon, as a mouse get connected.

System hangs at: (etc/logs/messages)

Jan  8 15:17:14 Stretch11 kernel: [   16.795565] fuse init (API version 7.26)
_[system hangs here, after plugging a mouse it continues]_
Jan  8 16:12:50 Stretch11 kernel: [  316.155022] random: crng init done
Jan  8 16:12:50 Stretch11 kernel: [  316.155036] random: 7 urandom warning(s) missed due to ratelimiting.
Jan  8 16:12:50 Stretch11 vncserver-x11[418]: ServerManager: Server started
Jan  8 16:12:50 Stretch11 vncserver-x11[418]: ConsoleDisplay: Found running X server (pid=458, binary=/usr/lib/xorg/Xorg)
Jan  8 16:12:51 Stretch11 vncserver-x11[418]: Connections: connected: 192.168.188.21::60722
Jan  8 16:12:52 Stretch11 vncserver-x11[418]: Connections: authenticated: 192.168.188.21::60722, as pi (f permissions)

(found out through plugging the mouse exactly at 16:12:50)

Workaround solution: install haveged.
Then it boots like a charm! Also without a mouse.

Please consider revising that step of the boot process:
The Raspberry Pi is predestined to work headless. Seeking for entropy from a mouse is not purposedly.
I have lost days, until I found the workaround and I am not the only one.
The fora have many similar issues and a lot of users are clueless, fiddling on the wrong gears...

Thank you for considering my issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions