Re: bpvo pool exhausted

From: Cameron Berkenpas <cam_at_neo-zeon.de>
Date: Wed, 28 Sep 2022 03:13:45 UTC
Hello,

I do not have a way to consistently reproduce this. I was finally able 
to get through recompiling all of the installed ports before I was able 
to test this.

Should this show up via sysctl? Because it does not:
sysctl machdep.moea64_bpvo_pool_size
sysctl: unknown oid 'machdep.moea64_bpvo_pool_size'

Should I be able to set this in /boot/loader.conf?

I did try setting it at boot. I'm not sure it did anything though. 
Nothing in dmesg.

The VM has 12 threads and 16GB of memory running 13.1-RELEASE-p2.

Maybe this is a new option in CURRENT?

On 9/27/22 11:54, Alfredo Dal'Ava Júnior wrote:
>
> Hi Cameron,
>
> In the loader prompt I type:
>
> set machdep.moea64_bpvo_pool_size=655360
> boot
>
> How are you testing it? What's the FreeBSD version and how much memory 
> do you have on it? As reference I tested it on VMs with 64GB of RAM in 
> the past.
>
> []'s
> Alfredo
>
> On Tue, Sep 27, 2022 at 2:41 PM Cameron Berkenpas <cam@neo-zeon.de> wrote:
>
>     Hello,
>
>     When recompiling my ports, I started getting periodic crashes on a VM
>     running on POWER9.
>
>     "bpvo pool exhausted".
>
>     The message says to try setting
>     machdep.moea64_allocated_bpvo_entries,
>     but this is apparently read-only. I've attached a screenshot of the
>     stacktrace.
>