From: Jaap Crezee <jaap@jcz.nl>
To: buildroot@busybox.net
Subject: [Buildroot] boot failure
Date: Sun, 6 May 2018 22:16:30 +0200 [thread overview]
Message-ID: <f49f99ee-cdff-a14d-8470-26917b6605c9@jcz.nl> (raw)
In-Reply-To: <2f8b7f67-4819-645d-2c97-c108656e78f5@micronovasrl.com>
Hello all,
> I'm experimenting the same thing with udev, this is my log:
> "
> [??? 5.334345] udevd[83]: starting version 3.2.5
> [??? 5.352869] random: udevd: uninitialized urandom read (16 bytes read)
> [??? 5.380840] random: udevd: uninitialized urandom read (16 bytes read)
> [??? 5.387495] random: udevd: uninitialized urandom read (16 bytes read)
> [??? 5.468700] udevd[84]: starting eudev-3.2.5
> [??? 6.445387] urandom_read: 1 callbacks suppressed
> [??? 6.445397] random: dd: uninitialized urandom read (512 bytes read)
> [??? 6.561425] random: dbus-uuidgen: uninitialized urandom read (12 bytes read)
> [??? 6.68793 random: dbus-uuidgen: uninitialized urandom read (8 bytes read)
> [??? 6.894495] random: crng init done
> [??? 6.897924] random: 2 urandom warning(s) missed due to ratelimiting
> "
>
> Since complains with dropbear with Enoch and udev with me,
> it seems something kernel related, need to debug it.
Please try using packages like rngd & haveged to make sure all RNG hardware features are used to initialize the kernel random number generator as
early as possible. If you can generate (sort of random) interrupts during boot that will also help to speed up the initialisation.
Jaap
prev parent reply other threads:[~2018-05-06 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 7:04 [Buildroot] boot failure Enoch W.
2018-05-06 8:32 ` Peter Korsgaard
2018-05-06 17:35 ` Giulio Benetti
2018-05-06 20:16 ` Jaap Crezee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f49f99ee-cdff-a14d-8470-26917b6605c9@jcz.nl \
--to=jaap@jcz.nl \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.