From owner-freebsd-arm@freebsd.org Wed Aug 1 02:09:56 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8F9C106CDA8 for ; Wed, 1 Aug 2018 02:09:55 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-22.consmr.mail.gq1.yahoo.com (sonic309-22.consmr.mail.gq1.yahoo.com [98.137.65.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74F2A8E588 for ; Wed, 1 Aug 2018 02:09:55 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: cxVoY2QVM1kUqaz.b6ZEtDbxgQUM6PlmWgIVnq3vxMt7eMLJT1MVZyv4Geo0ukX kUngLqr8ZDtAImF5ApAjFgfdttPsquJfHGviQrZCnZK7Jyu75FRWfn9UuH1xwjPqOZbzz3746MNp qJOEKiS2vMQukiXG5D8iD8HPekH7mbpse1SguO0097Q2U3dnY4R8O6Bm5FpwjGdrYxgSMWhHM4fW VFOLLpCTbgQZ9DTsZj5lSg14oXCgabLTlsNza.uIhVIDNUELoelEwe_Xo2lOIyA6DkrPHT52MolU kFdodWyHN40GAdcdNo_llef_yf1Tku9gyFiqDK0dlGJmLHhlJZYGgJA_i.JOrW8gxJ7lZRSqfmMz X1qxVvRGh7QR5GzqENB5tvkEdSWByvHThJbCA37v1kc6aBcr2ekygC.jh12VZ1nBbcgC4EP7XQ65 Lc51rZuXpj85t9AB8CjDP6hUh5rzJOIBohHq82vx2.rK9CycYnj54Qhrheuvdhk.ZgEEkgA5CCRw jlxWwyzhHr6OqC7L_WjTEGX4IwD0YRlaGOpF70468TLZS54NSWasym_wLym6G7FgzJFRiDafuwJ4 6vS_sVrGUcBqbEDJ_d.aGfJuAxBrkMxAhTg00r_kirQEoR1Rj2PPmTFvysPwEAEoMh0S5ntSv08w tN_Ms7OXWq0x1aiBWYd8yBAHdoWZNwNXPobB8_iRxg5wpj8DoDReDoLCVzV7vfxyMO.hpslPL6t2 a_dkr0F7Udf7vTUMSKHdxnQTsDTtRiwpMz4KquzIBGY8EbysJXoYpkXLlTKon.pjsoc5bI8.QOIm Q0fI4s_j7x2T3_aogmScGOCrQywC.baFKwkVPpNtTMFOl24NyHzo3Ys1ybJn9UurtddOPa0CaxKk 3Nb2_dz.6_vewcZf_uejyS9vLfMgwLSVwNMH_SaxMNnSrZMY_W5lNRJPFfI132owohKT0.DydEq3 PkzC.sUpnacfc7l7tR2KdosD2T3doENki2c1adR8Wvw9_6veOfihsHTvc1LDGWhW6Gm0LPiMw7th 0iZjrP45Atb0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.gq1.yahoo.com with HTTP; Wed, 1 Aug 2018 02:09:47 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp424.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 63171a5e30b10ec42b4410fce2c6e214; Wed, 01 Aug 2018 02:09:44 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: RPI3 swap experiments From: Mark Millard In-Reply-To: <20180731231912.GF94742@www.zefox.net> Date: Tue, 31 Jul 2018 19:09:43 -0700 Cc: "Rodney W. Grimes" , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2222ABBD-E689-4C3B-A7D3-50AECCC5E7B2@yahoo.com> References: <20180731153531.GA94742@www.zefox.net> <201807311602.w6VG2xcN072497@pdx.rh.CN85.dnsmgr.net> <20180731191016.GD94742@www.zefox.net> <23793AAA-A339-4DEC-981F-21C7CC4FE440@yahoo.com> <20180731231912.GF94742@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2018 02:09:56 -0000 On 2018-Jul-31, at 4:19 PM, bob prohaska wrote: > On Tue, Jul 31, 2018 at 01:49:57PM -0700, Mark Millard wrote: >> On 2018-Jul-31, at 12:10 PM, bob prohaska = wrote: >>=20 >>=20 >>> Some weeks (months?) ago there was a thread about swap being broken. = Was >>> that in any way related to what I'm seeing? >>=20 >> There was some ZFS context stuff that seemed to be independent of >> UFS stuff relative to memory use. I continue to see reports tied >> to ZFS contexts. >>=20 >> But I'm not sure if this is in any way related to what you are >> calling "swap being broken". I do not remember anything about >> swap being directly broken for swap partitions. (Swap files are >> a different issue and are problematical.) >>=20 >=20 > The thread I'm referring to starts with=20 > = https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069728.html = and titled > " swapping is completely broken in -CURRENT r334649? " >=20 > There's no mention whether ARM is affected, just "certain hardware".=20= > It looks like a bug was introduced in r329882 and fixed in r334752. > Workarounds suggested include=20 > sysctl vm.pageout_update_period=3D0 > and > sysctl vm.pageout_update_period=3D1000.=20 >=20 > Maybe the first will turn OOMA off, and the second delay it?=20 > On RPi the value is 600. The one correspondent who tried 1000 > said it didn't help, maybe zero is a better guess. For me it's > a shot in total darkness either way 8-)=20 In that thread is the message: = https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069835.html that has a patch for dumping out more information to demsg before it does the kill: diff --git a/sys/vm/vm_pageout.c b/sys/vm/vm_pageout.c index 264c98203c51..9c7ebcf451ec 100644 --- a/sys/vm/vm_pageout.c +++ b/sys/vm/vm_pageout.c @@ -1670,6 +1670,8 @@ vm_pageout_mightbe_oom(struct vm_domain *vmd, int = page_shortage, * start OOM. Initiate the selection and signaling of the * victim. */ + printf("v_free_count: %u, v_inactive_count: %u\n", + vmd->vmd_free_count, = vmd->vmd_pagequeues[PQ_INACTIVE].pq_cnt); vm_pageout_oom(VM_OOM_MEM); =20 /* Mark Johnston also mentions "sysctl vm" output as proving more contextual information. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)