From owner-freebsd-arm@freebsd.org Tue Jul 23 19:44:01 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C2EF6B181F for ; Tue, 23 Jul 2019 19:44:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4288D71EBF for ; Tue, 23 Jul 2019 19:44:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x6NJhowG032968 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 23 Jul 2019 12:43:51 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x6NJhn2m032967; Tue, 23 Jul 2019 12:43:49 -0700 (PDT) (envelope-from fbsd) Date: Tue, 23 Jul 2019 12:43:49 -0700 From: bob prohaska To: Jamie Landeg-Jones Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Lethargic rpi3, but seemingly still running Message-ID: <20190723194349.GA32898@www.zefox.net> References: <20190718034838.GA1921@www.zefox.net> <201907180958.x6I9wBF8075274@donotpassgo.dyslexicfish.net> <20190718151858.GB4325@www.zefox.net> <20190718182050.GL2342@funkthat.com> <20190721005135.GA18642@www.zefox.net> <201907230419.x6N4JRYZ069168@donotpassgo.dyslexicfish.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201907230419.x6N4JRYZ069168@donotpassgo.dyslexicfish.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 4288D71EBF X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.15 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.09)[ip: (0.36), ipnet: 50.1.16.0/20(0.18), asn: 7065(-0.04), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.71)[0.708,0]; NEURAL_HAM_LONG(-0.05)[-0.045,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.51)[0.509,0]; MX_GOOD(-0.01)[cached: www.zefox.net]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2019 19:44:01 -0000 On Tue, Jul 23, 2019 at 05:19:27AM +0100, Jamie Landeg-Jones wrote: > bob prohaska wrote: > > > Here's a snippet of systat -v 1 output while un-tarring firefox files. > > %busy was close to zero, it looks like there's congestion or a deadlock > > writing to the microSD card. At the time things like cd and ls were > > very slow to respond (tens of seconds) > > > > 28 pdpgs cpu2:ast > > Disks mmcsd da0 pass0 intrn cpu3:ast > > KB/t 12.00 0.00 0.00 152904 wire 9 cpu0:preem > > tps 5 0 0 80072 act 51 cpu1:preem > > MB/s 0.06 0.00 0.00 671344 inact 80 cpu2:preem > > %busy 213 0 0 120 21104 27 cpu3:preem > > You say "close to zero", but it's 213(!) in the output you gave! > Sorry, I was referring the %idle number above the bargraph and inverting the fraction, without noticing the %busy in the Disks output. At the moment the same machine is compiling clang8 with about 900M of swap in use, here is another sample: Disks mmcsd da0 pass0 264 intrn cpu3:ast KB/t 5.51 5.77 0.00 169680 wire 641 cpu0:pree tps 461 457 0 645096 act 1612 cpu1:pree MB/s 2.48 2.58 0.00 2280 inact 1522 cpu2:pree %busy 77 50 0 Swap is on both mmcsd and da0 (Samsung Evo+ microsd and a Sandisk usb3 flash drive). > However, I suspected something like that - high %busy whilst little actual > transfers taking place. I've seen it before, along with the characteristics > you describe, but unfortunately I don't have a fix. > So far I think the problem has only been obvious when bsdtar is running. If there's another way to provoke it that might be interesting to try. Thanks for reading more closely than I wrote! bob prohaska