From owner-freebsd-arm@freebsd.org Tue Jun 26 14:43:11 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 5858C1029995 for ; Tue, 26 Jun 2018 14:43:11 +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 B8D5673730 for ; Tue, 26 Jun 2018 14:43:10 +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 w5QEhIfp019573 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Jun 2018 07:43:19 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5QEhICZ019572; Tue, 26 Jun 2018 07:43:18 -0700 (PDT) (envelope-from fbsd) Date: Tue, 26 Jun 2018 07:43:18 -0700 From: bob prohaska To: Jamie Landeg-Jones Cc: imp@bsdimp.com, freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments, was Re: GPT vs MBR for swap devices Message-ID: <20180626144318.GC17293@www.zefox.net> References: <1D86911D-20D1-494A-822B-1C07C5598CB1@yahoo.com> <10CAC122-399D-459E-9153-ABD7E753777E@yahoo.com> <20180623143218.GA6905@www.zefox.net> <03C2D3C4-6E90-4054-AF79-BD7FE2B7958D@yahoo.com> <20180624231020.GA11132@www.zefox.net> <20180626052451.GA17293@www.zefox.net> <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2018 14:43:11 -0000 On Tue, Jun 26, 2018 at 11:40:11AM +0100, Jamie Landeg-Jones wrote: > Warner Losh wrote: > > > > > _vfs_done():da0d[WRITE(offset=51819347968, length=131072)]error = 5 > > > > g_vfs_done():da0d[WRITE(offset=51819479040, length=28672)]error = 5 > > > > g_vfs_done():da0d[READ(offset=59586936832, length=32768)]error = 5 > > > > g_vfs_done():vm_fault: pager read error, pid 823 (tcsh) > > > > > > > The device is broken if you get this. Period. I don't know if it is > > hardware, or software, but it is not a reliable storage device. Until > > that's fixed, you'll continue to have a terrible experience with it. > > > > [ ... ] > > > Sorry to sound so harsh, but the data has been consistent on this for > > everything you've reported: it works for a while, then we get a bunch of > > errors then a reboot. We need to start narrowing down which of these three > > broad classes of root causes it is. I'd rank actual bad thumbdrive last on > > the list. It's a tossup for me between missing quirk and a bug in the rpi > > usb driver that manifests itself only under heavy load. IIRC, you said one > > of rpi2/3 works and the other doesn't, which would suggest a usb bridge > > driver problem... > > For what it's worth, I had the same errors on a rpi3 a few months ago, and > eventualy gave up "to sort it tomorrow" - it hasn't been powered on since, but > I still want to get it working. > It might be worth quite a lot 8-) > The system would run fine, but give the vfs errors on the 128GB usb thumb > drive every week - like clockwork, when one of the heavier periodic jobs ran. > That is something I've not seen. > I was running the latest CURRENT at the time. The thumb drive works fine elsewhere, > and indeed - did on the same hardware when I test installed a linux install, > and thrashed the hell out of it. > > I'll fire it up again - hopefully I'll still have the same results, and with 2 > of us, we may find the cause quicker. > > (n.b. i never had swap errors, but I can't recall if i ever configured swap on the usb > drive) > To be clear, the USB thumb drive in question wasn't supporting a swap partition at the time of the error message quoted above. /da0d held /usr. Swap was on the boot microSD card and was deliberately too small (1 GB) to let -j4 buildworld run to completion. All attempts to use swap on the suspected USB flash drive resulted in OOMA kills, all attempts to use sufficient swap (2 GB or more) not on the suspected USB flash drive resulted in successful -j4 buildworlds. Thanks for writing! bob prohaska