> On 11 Sep 2017, at 11:25, Borja Marcos wrote:
>
>> Since I’ve updated a machine to 11.1-STABLE I am seeing a rather unusual
>> growth of Wired memory.
>>
>> Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE and
>> 11.1-STABLE?
vmstat -z and vmstat -m follow
% vmstat -z
On Tue, 2017-09-12 at 09:20 +1000, Morgan Reed wrote:
> In all likelihood the process wasn't "hung" per-se, more likely
> random
> hadn't been seeded yet and as such you *can't* get 4096b of entropy
> out of
> it (so the process was attempting to do its job, just nothing on the
> device).
>
> The
In all likelihood the process wasn't "hung" per-se, more likely random
hadn't been seeded yet and as such you *can't* get 4096b of entropy out of
it (so the process was attempting to do its job, just nothing on the
device).
The issue is basically that there are very few "good" entropy sources in a
I just had a VM running in Google's cloud become totally useless, and I
tracked it down to the save-entropy operation.
Basically this process was sucking up all CPU, even when nothing else
running other than my ssh shell:
% ps axuw803
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME CO
> On 11 Sep 2017, at 11:09, Borja Marcos wrote:
>
>
> Hi,
>
> Since I’ve updated a machine to 11.1-STABLE I am seeing a rather unusual
> growth of Wired memory.
>
> Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE and
> 11.1-STABLE?
Evil Mailman scrubbed my attachment
Hi,
Since I’ve updated a machine to 11.1-STABLE I am seeing a rather unusual growth
of Wired memory.
Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE and
11.1-STABLE?
Thanks!
___
freebsd-stable@freebsd.org mailing list
https:
