From nobody Wed Sep 28 14:40:47 2022 X-Original-To: ppc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Mczgk04Cqz4YHQ7 for ; Wed, 28 Sep 2022 14:40:50 +0000 (UTC) (envelope-from cam@neo-zeon.de) Received: from neo-zeon.de (neo-zeon.de [70.229.12.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.neo-zeon.de", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mczgj054Gz3fH8 for ; Wed, 28 Sep 2022 14:40:48 +0000 (UTC) (envelope-from cam@neo-zeon.de) Received: from neo-zeon.de (localhost [::1]) by neo-zeon.de (OpenSMTPD) with ESMTP id 2c4a8779 for ; Wed, 28 Sep 2022 07:40:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=neo-zeon.de; h= content-type:message-id:date:mime-version:subject:to:references :from:in-reply-to; s=1; bh=kHF8BtJr5dXxlbDLVrFMtotUg+c=; b=VAWLE jcLO7wsnZMmVdi0hXo33umFqCZN92muz5bGnf+CA8blBex4rl3cFTtLNS0dfUa2y GS/qHWXXGJj6mE91QBOWyDapgFrdNcY0SUYUnIYR6aIXcJ+5QjdiBsERXhBlTole i1ui28WCRsoS1+CRttNVjppRsmj1B8HSWPj0gg= Received: by neo-zeon.de (OpenSMTPD) with ESMTPSA id 3904c714 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Wed, 28 Sep 2022 07:40:46 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------CEGdF6fvNR14wggNWbNg07H6" Message-ID: Date: Wed, 28 Sep 2022 07:40:47 -0700 List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Subject: Re: bpvo pool exhausted To: ppc@freebsd.org References: <6ddde0d6-03d8-6b54-fb5d-9589e3e5c1e3@neo-zeon.de> <5fa07e44-b840-7a2d-996c-755b7f0bed7e@neo-zeon.de> Content-Language: en-US From: Cameron Berkenpas In-Reply-To: X-Rspamd-Queue-Id: 4Mczgj054Gz3fH8 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=neo-zeon.de header.s=1 header.b="VAWLE jc"; dmarc=pass (policy=quarantine) header.from=neo-zeon.de; spf=pass (mx1.freebsd.org: domain of cam@neo-zeon.de designates 70.229.12.130 as permitted sender) smtp.mailfrom=cam@neo-zeon.de X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.98)[-0.983]; DMARC_POLICY_ALLOW(-0.50)[neo-zeon.de,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[neo-zeon.de:s=1]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[ppc@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[neo-zeon.de:+]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:7018, ipnet:70.228.0.0/14, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ppc@freebsd.org]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N 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 > 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 >> 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

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--