Re: bpvo pool exhausted
- Reply: Cameron Berkenpas : "Re: bpvo pool exhausted"
- In reply to: Cameron Berkenpas : "Re: bpvo pool exhausted"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 28 Sep 2022 12:31:33 UTC
Cameron, This is a boot-only option that can't be tuned by sysctl. You really need to set it in the loader prompt if just testing or add the following to /boot/loader.conf to make it permanent: machdep.moea64_bpvo_pool_size=655360 This option is not new but before 13.0-RELEASE there was a bug preventing users from setting a value larger than the default (327680). This was fixed by change https://cgit.freebsd.org/src/commit/?id=95a8fce118b24c0a7656f4ded4690210d9998e24. []'s, Alfredo On Wed, Sep 28, 2022 at 12:13 AM Cameron Berkenpas <cam@neo-zeon.de> wrote: > 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. >> > >