From owner-freebsd-arm@freebsd.org Mon Mar 5 05:30:19 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 AB613F32B41 for ; Mon, 5 Mar 2018 05:30:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2717F83BD4 for ; Mon, 5 Mar 2018 05:30:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22f.google.com with SMTP id p78so16583167iod.13 for ; Sun, 04 Mar 2018 21:30:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=iiRLT6sfk4gu+OPTBKEY8f0NSglpdajcDgwhpYNIhLA=; b=j9WGKqnG2X+FYTfDpmicBaPqOOls7N2wcuxSASK766gPZNbX90/bUY8GPuyL7xk6rj b1LkfwPMnGgDouy5FHeJ/lvCH6V9nb7rtEKtQK2CTDN74TLZ8Aestciv04z8n7OCB3L8 qzhzC19Fyrs45vF206I56/OCoWBEW+HJGHD8+7wbYL8lkfz0/AKOyHv18+oUEzvj6gnQ QMPLkOzRuLzXh2xpNnxX6CFkKuBPtXn++a7Nk+k3KwlyF4/tgrDgyjVE7m1Z0q3l9tjC GyXr6sunzGUuKv6kQMZtpWVpxn6xSzThpcsX+Xj6kFVO0EO3ExU8vM/z/f2TjDuyc5fy rkfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=iiRLT6sfk4gu+OPTBKEY8f0NSglpdajcDgwhpYNIhLA=; b=Kh1h7DMBZp7pm7DtbGXAOuENPlB3NQvBbCz2S9VfnNtnewbhb8a7qr0X63wiP8wJKL PQvh/0gDf1h5j9cmAX+dsR6FayI9HVLFM5hi25k2xfv+aV+PPpRF9nHTzY3ZSQ3gUMtz pfpAwQTvopoUXF/S8eVS+w7hh8TpreU0eIxAXbJMp6vxNHNGItWNhYTUZfaOB5wcNeu4 fnLF9KiecwvAsqPiVYFGBsP2Uyudj9dKknClw1dz8R+TfP0yrdQUW+tWd8x3maQilQ8l ToXosyB+/CQTzoQQxcjtR7/YeeOITxdWVTiZW4rdR4NO6L87k/rqHwTjjh+BvfigpY/Q nlVg== X-Gm-Message-State: APf1xPClHxG98wO5Xklbh2dkqn5LgOJQiC8WU6P/gd38dMNb3V9/fVus BK4J1lS1NOoZz+YinQ2+Ewww/qrMRIdejLIx0+QETA== X-Google-Smtp-Source: AG47ELu0tIzbNLnOcD8tSF/R04C6LAef8R6ad8Jvo+BosVvDjXNWmNDJceYeAs20HQPKS5T3BJIlQLgd0Qkk3HXvSYQ= X-Received: by 10.107.2.6 with SMTP id 6mr15606405ioc.117.1520227818409; Sun, 04 Mar 2018 21:30:18 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sun, 4 Mar 2018 21:30:17 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180305045723.GA47820@www.zefox.net> References: <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> From: Warner Losh Date: Sun, 4 Mar 2018 22:30:17 -0700 X-Google-Sender-Auth: E8AMPtj56PeX4dCzEpELpjE2Szg Message-ID: Subject: Re: Is maximum swap usage tunable? To: bob prohaska Cc: Ian Lepore , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Mon, 05 Mar 2018 05:30:20 -0000 On Sun, Mar 4, 2018 at 9:57 PM, bob prohaska wrote: > On Sun, Mar 04, 2018 at 01:40:03PM -0800, bob prohaska wrote: > > make -j4 buildworld > > > > was started with the usb-hosted swap partition turned off, leaving only > > the microSD-hosted swap running. It got past the first cycle of > llvm-tblgen > > showing only half of the one GB available swap in use, with no errors or > > warnings. There is some decent chance it'll run to completion, probably > > late tomorrow. For now I'll just see how far it gets. > > > The j4 buildworld using only 1 GB swap on microSD really ran out of > swap after a prolonged (half hour or so) interval of swread and pfault > status in top and a stream of > > swap_pager_getswapspace(4): failed > Yes. This meant that the swapper tried to get space, but failed. It prints this once, then all further requests print nothing until one succeeds and then it prints it again. So you are rockering back and forth on the edge until it finally fails... > Mar 4 20:02:09 www kernel: pid 25154 (c++), uid 0, was killed: out of > swap space > and kills something, the C++ compiler. A good choice if you are low on space. > on the console. There were no "indefinite wait" messages at all > That just means that the SD card wasn't overwhelmed this time.... > It appears that swap on microSD worked much better than > swap on USB, only failing after hitting 85% or more of utilization > and even then not giving up easily. > You likely have power issues then. Power issues and/or cheap-ass USB<->SD adapters can cause the extremely slow writes that lead to the indefinite wait. > The log files for buildworld and gstat are at > http://www.zefox.net/~fbsd/rpi3/swap_issues/ > on the chance they're worth looking at. I'd look at power. And add more swap. Warner > > bob prohaska > > > > > >