On Tue, Jan 31, 2017 at 05:54:37PM +0100, Martin Husemann wrote: > On Tue, Jan 31, 2017 at 11:45:55AM -0500, Thor Lancelot Simon wrote: > > The only time we've ever really dug into it, I believe, the user decided > > the failures were right around the expected failure rate. Can you help > > gather more data? > > Good point, and I am not sure this might cover my case as well - will have > a look and start gathering better data.
Hmm, for a simple start: Jan 31 16:00:16 night-owl /netbsd: Kernel RNG "7517 14 4" monobit test FAILURE: 9709 ones Jan 31 16:00:16 night-owl /netbsd: cprng 7517 14 4: failed statistical RNG test Jan 31 20:20:12 night-owl /netbsd: Kernel RNG "11702 2 8" runs test FAILURE: too many runs of 4 0s (395 >= 384) Jan 31 20:20:12 night-owl /netbsd: cprng 11702 2 8: failed statistical RNG test Jan 31 20:20:25 night-owl /netbsd: Kernel RNG "16549 4 9" runs test FAILURE: too few runs of 2 0s (1107 <= 1114) Jan 31 20:20:25 night-owl /netbsd: cprng 16549 4 9: failed statistical RNG test Jan 31 21:21:05 night-owl /netbsd: Kernel RNG "7429 2 9" poker test failure: parameter X = 2.8640 Jan 31 21:21:05 night-owl /netbsd: cprng 7429 2 9: failed statistical RNG test Jan 31 21:21:47 night-owl /netbsd: Kernel RNG "17166 149 10" long run test FAILURE: Run of 26 0s found Jan 31 21:21:47 night-owl /netbsd: cprng 17166 149 10: failed statistical RNG test This is my amd64 notebook while doing a few ssh sessions and a pkg_chk rebuild. Nothing involved that really (AFAIU) needs serious ammounts of entropy. Is there a simple way to get usage statistics? Martin
