Hi,

I’ve stumbled upon this too with recently upgraded machine (to NetBSD 8.0_BETA 
(GENERIC.201803261630Z))

Kernel RNG “5887 68 5” runs test FAILURE: too many runs of 1 1s (2691 >=2685)
cprng 5887 68 5: failed statistical RNG test

The difference here is that the machine also loses network connectivity (& the 
USB keyboard).
unplugging / replugging the keyboard doesn’t show that the kernel is still 
working on the console.
(you’d expect to see output about the usb device unplugged / replugged)

I also tried to add a watchdog to reboot the server then it hangs, but that 
isn’t working, so it’s a weird state it hangs in…

# wdogctl
Available watchdog timers:
        ipmi0, 0 second period
        tco0, 30 second period [armed, user tickle, pid 441]

Any ideas ?

/P

> On 20 May 2015, at 23:46, Paul Goyette <p...@vps1.whooppee.com> wrote:
> 
> Perhaps we could make the messages a little bit less frightening?
> 
> Perhaps s/FAILURE/NOTICE/
> 
> 
> 
> On Wed, 20 May 2015, Christos Zoulas wrote:
> 
>> In article 
>> <pine.neb.4.64.1505201111400.29...@6bone.informatik.uni-leipzig.de>,
>> <6b...@6bone.informatik.uni-leipzig.de> wrote:
>>> Hello,
>>> 
>>> dmesg reported:
>>> 
>>> Kernel RNG "2105 0 2" runs test FAILURE: too many runs of 3 1s (728 > 723)
>>> cprng 2105 0 2: failed statistical RNG test
>>> 
>>> Any ideas what could be the problem?
>>> 
>>> 
>>> kernel version: NetBSD 7.99.9
>>> distribution: netbsd-7 (version May 11)
>> 
>> It is not really a problem. Things like this can happen. If you see messages
>> like this continuously, then there is a problem. In current a bunch of RNG
>> diagnostic messages have been turned on in order to evaluate the quality
>> of the random number generation.
>> 
>> christos
>> 
>> 
> 
> -------------------------------------------------------------------------
> | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
> | (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
> | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org  |
> -------------------------------------------------------------------------


Reply via email to