[ermanno]

IIRC the problem is with the via rng, but it is simply bugged :-) it is based on thermal effects, and when the load is high and the CPU temp high vthe via rng returns mostly 1s, it is easy to check on a board using it :-) rngd (which I used before) can detect this condition and switch to another source (I used aveged). But randomness is not the problem for me ATM (I think at least).

IIRC libressl should have supported padlock and AESNI, I have no political reason to use those CPU extensions or not, but some speed could be welcome to use iscsi over ssh tunnels and file transfers over SSL :-)
And nginx using so much CPU is also requiring using more Watts of electricity and that is bad for the environment (and my wallet). Imagine how much CO2 are releasing in the atmosphere all those CPU doing AES encriptions in software