svn commit: r256377 - in head: problems on ARM BEAGLEBONE

[Ian Lepore]

On Sat, 2013-10-12 at 12:57 +0000, Mark Murray wrote:
> Author: markm
> Date: Sat Oct 12 12:57:57 2013
> New Revision: 256377
> URL: http://svnweb.freebsd.org/changeset/base/256377
> 
> Log:
>   Merge from project branch. Uninteresting commits are trimmed.
>   
>   [snip]
> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***

I rebuilt my beaglebone sandbox today after syncing to the latest
-current and this happened:


 FreeBSD 11.0-CURRENT #4 r256393: Sat Oct 12 17:05:43 MDT 2013
 ilepore at revolution.hippie.lan:/local/build/staging/freebsd/bb/obj/arm.armv6/local/build/staging/freebsd/bb/src/sys/BB arm
 ...
 random device not loaded; using insecure entropy
 Falling back to <Dummy entropy device that always blocks> random adaptor
 random: <Dummy entropy device that always blocks> initialized
 ...
 Setting hostid: 0xdcf01d1d.
 Entropy harvesting:sysctl: unknown oid 'kern.random.sys.harvest.interrupt': No such file or directory
  interruptssysctl: unknown oid 'kern.random.sys.harvest.ethernet': No such file or directory
  ethernetsysctl: unknown oid 'kern.random.sys.harvest.point_to_point': No such file or directory
  point_to_pointsysctl: unknown oid 'kern.random.sys.harvest.swi': No such file or directory
  swi.
 Starting file system checks:
 mount_nfs: can't update /var/db/mounttab for 172.22.42.240:/bb
 Mounting local file systems:.
 Writing entropy file:random: dummy device blocking on read.


If you remove "device random" from the config then it says only "random
device not loaded; using insecure entropy" early in boot, and it doesn't
block during rc processing.  What's being used in that case,
arc4random()?

It looks like the cause of the problem is that both the dummy and the
yarrow generators register, dummy first, and so it gets chosen even
though yarrow is available.

-- Ian