From owner-freebsd-arm@freebsd.org Sun Feb 18 03:38:52 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 325A5F0B268 for ; Sun, 18 Feb 2018 03:38:52 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1EDE7FA82 for ; Sun, 18 Feb 2018 03:38:51 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 44A4D20D96; Sat, 17 Feb 2018 22:38:51 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 17 Feb 2018 22:38:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=yTD2gSioJP6liOwswXIN6NI9II+ME Gg4sSEV57LLwTg=; b=JZdp1n1nuWz5AD9D5uusz+xKUp+XzddRtOiLu/wtJj+qP Ru7YB+wdZQ2NV2tMAF3tarRYetIHkWU+R3lEdclVhaIYwKqJXw7ko3OZlgW5uF5h N1W1S0uQ2MNUUBvXyolmiFpXyjMyOcI0n8m9EcA/BCjSAl+4SAetXpdtpJWP3w3S vWI69S91h1/ac/xdgHRLJ00FY4Iw+/0j7TZ65qVlDzm5NIVRkMYZg89gwr3dP81k 6ybe46MC0kzm3eBV6mOk25+8PY5rxkJoU3KgZKkdQYjOOT0p+aQLgtusE0d9QxdA hTxwlRmom9KGP7wpiYm9RM61k8I0l92NSp18gDzBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=yTD2gS ioJP6liOwswXIN6NI9II+MEGg4sSEV57LLwTg=; b=czQQyWVjSdAdW4FmVu5J8z njKQF8MlHb1x30iZGAyfF8FPa3+WsxLiqqFCbjUluCIKgdbTYV5leT0TUn1RsIlx bFhe4YsZmXdUFze8+5c6d+fWKIcJrChcRr12e/4kPPhKSuyo8fY7YcOWPlNSnore xyxtaTEn3yQFX/8F1IGBqqnoeRPqO8k3sLMLG4vsDyj1jLB6TqIPAeqjmTQMdgzE 0nK8MdupG9VCOoCSiLxPs9gHfQJ9qkibwge/3qUS30DTeJmRdARBKhUGfYWT5jqx vCjJjogq0M2Mp3YZ2IWfUruHi8uRNMcxpHEjzitf9sHqVp95Fqgk0az9DBL8UuEA == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id BD02E2469C; Sat, 17 Feb 2018 22:38:50 -0500 (EST) Subject: Re: Pi3 out of swap at < 50% To: bob prohaska Cc: freebsd-arm@freebsd.org References: <20180217162732.GA93736@www.zefox.net> <1518885801.91697.2.camel@freebsd.org> <9bf0ca6e-1916-3f4d-71fe-0515fe6a717f@zyxst.net> <20180218003840.GD93736@www.zefox.net> From: tech-lists Message-ID: <3d2bd5e3-4567-cdfe-04d4-b572371a212e@zyxst.net> Date: Sun, 18 Feb 2018 03:38:49 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180218003840.GD93736@www.zefox.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 03:38:52 -0000 On 18/02/2018 00:38, bob prohaska wrote: > The arm64 RPI3 also has 2 GB configured in two equal partitions, one > on the USB flash drive and one on the microSD card used for booting. > It's claiming "out of swap" with only about 50% usage. Swapinfo shows > both partitions are being used, so that's not the problem. Kernel and > world are a couple weeks out of sync, which might be a problem but it > can't be checked until buildworld runs to completion, which it hasn't. In that situation I'd deactivate the swap on the card, and make a few swap partitions on the flash drive. I used to run into the sort of difficulty you're seeing if swap was on the microsd. It's not just swap though; enough i/o activity on the card and it starts blocking. You can tell it's happening if in another terminal if you type sync. It takes several seconds (sometimes tens of seconds) to return. I'd like to be able to set async on the connected HD but it seems even when it's set in fstab it doesn't show up when the mount command is issued. The HD connects via a powered hub btw. These days I don't do updates or compiling on the rpi3 itself now that poudriere/synth can cross-compile ports. If I need to update the OS I'll use crochet to build an image from whatever sources on a beefy amd64 then restore my data. I must have gone through dozens of microsd cards before arriving at this solution. Some just completely fail, others suddenly become read-only. There's probably a solution in dd'ing the card image to a more powerful computer, mounting the image and crossbuilding into it which would be more efficient I think but I haven't tried it yet. -- J.