Date: Wed, 28 Sep 2022 07:40:47 -0700 From: Cameron Berkenpas <cam@neo-zeon.de> To: ppc@freebsd.org Subject: Re: bpvo pool exhausted Message-ID: <eb75223b-e7a2-18d4-104d-29d1845d1ac7@neo-zeon.de> In-Reply-To: <CAOpTx7Ho5gA=vRhD7vYBE-UsnpNPuGxwcgZSBc-SiUS3NO67UQ@mail.gmail.com> References: <6ddde0d6-03d8-6b54-fb5d-9589e3e5c1e3@neo-zeon.de> <CAOpTx7G0faPob9yO5Z_DtDLeipaAsc9R2oSmnoRd8PU43MRDhw@mail.gmail.com> <5fa07e44-b840-7a2d-996c-755b7f0bed7e@neo-zeon.de> <CAOpTx7Ho5gA=vRhD7vYBE-UsnpNPuGxwcgZSBc-SiUS3NO67UQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------CEGdF6fvNR14wggNWbNg07H6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Thank you for the explanation. I suspect this will fix the issue! On 9/28/2022 5:31 AM, Alfredo Dal'Ava Júnior wrote: > 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. >> > --------------CEGdF6fvNR14wggNWbNg07H6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p>Thank you for the explanation.</p> <p>I suspect this will fix the issue!<br> </p> <div class="moz-cite-prefix">On 9/28/2022 5:31 AM, Alfredo Dal'Ava Júnior wrote:<br> </div> <blockquote type="cite" cite="mid:CAOpTx7Ho5gA=vRhD7vYBE-UsnpNPuGxwcgZSBc-SiUS3NO67UQ@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr"> <div>Cameron,</div> <div><br> </div> <div>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:<br> </div> <div><br> </div> <div>machdep.moea64_bpvo_pool_size=655360</div> <div><br> </div> <div>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 <a href="https://cgit.freebsd.org/src/commit/?id=95a8fce118b24c0a7656f4ded4690210d9998e24" moz-do-not-send="true" class="moz-txt-link-freetext">https://cgit.freebsd.org/src/commit/?id=95a8fce118b24c0a7656f4ded4690210d9998e24</a>. <br> </div> <div><br> </div> <div>[]'s,</div> <div>Alfredo<br> </div> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Wed, Sep 28, 2022 at 12:13 AM Cameron Berkenpas <<a href="mailto:cam@neo-zeon.de" moz-do-not-send="true" class="moz-txt-link-freetext">cam@neo-zeon.de</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div> Hello,<br> <br> 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.<br> <br> Should this show up via sysctl? Because it does not:<br> sysctl machdep.moea64_bpvo_pool_size<br> sysctl: unknown oid 'machdep.moea64_bpvo_pool_size'<br> <br> Should I be able to set this in /boot/loader.conf?<br> <br> I did try setting it at boot. I'm not sure it did anything though. Nothing in dmesg.<br> <br> The VM has 12 threads and 16GB of memory running 13.1-RELEASE-p2.<br> <br> Maybe this is a new option in CURRENT?<br> <br> <div>On 9/27/22 11:54, Alfredo Dal'Ava Júnior wrote:<br> </div> <blockquote type="cite"> <div dir="ltr"> <div><br> </div> <div>Hi Cameron,</div> <div><br> </div> <div>In the loader prompt I type:<br> </div> <div><br> </div> <div>set machdep.moea64_bpvo_pool_size=655360</div> <div>boot<br> </div> <div><br> </div> <div>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. </div> <div><br> </div> <div>[]'s</div> <div>Alfredo<br> </div> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Tue, Sep 27, 2022 at 2:41 PM Cameron Berkenpas <<a href="mailto:cam@neo-zeon.de" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">cam@neo-zeon.de</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br> <br> When recompiling my ports, I started getting periodic crashes on a VM <br> running on POWER9.<br> <br> "bpvo pool exhausted".<br> <br> The message says to try setting machdep.moea64_allocated_bpvo_entries, <br> but this is apparently read-only. I've attached a screenshot of the <br> stacktrace.<br> </blockquote> </div> </blockquote> <br> </div> </blockquote> </div> </blockquote> </body> </html> --------------CEGdF6fvNR14wggNWbNg07H6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eb75223b-e7a2-18d4-104d-29d1845d1ac7>