Since updating to kirkstone from hardknott, after boot rngd maxes out my rpi4's processor for minutes initializing JITTER. The sustained CPU usage was triggering my resource monitoring alerts. Changing config to disable jitter with -x jitter stops the initialization process and uses just the pi's hardware rng source. Since that solved the problem I disabled building rng-tools with libjitterentropy enabled.
I submitted the change to meta-raspberrypi (pull #1057) where kraj noted that the CPU spike is seen even on qemu so the change should go in the core layer.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#165175): https://lists.openembedded.org/g/openembedded-core/message/165175 Mute This Topic: https://lists.openembedded.org/mt/90845997/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
