From owner-freebsd-arm@freebsd.org Tue Jun 26 14:38:07 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 10B451029484 for ; Tue, 26 Jun 2018 14:38:07 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-3.consmr.mail.bf2.yahoo.com (sonic301-3.consmr.mail.bf2.yahoo.com [74.6.129.42]) (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 9C8E973137 for ; Tue, 26 Jun 2018 14:38:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 2DMXJoEVM1k0wfwIM8T.PGA5sgnYJMsD0zN64VJ6UH0Boj.GpHZsSvjxRHBTR9u WWeKCO6qOor33H6u7_TWy18TludsvlY5pl3G_6NkiayEqoLfQUo_1M1LOzZvWUwSNYkziP1lfwA5 bq_Geb_OcS_Ju4zuUBjrFfTcalufPmGs7uZc7BwC57UghEXVA4xd8Hoxh4KBMNvf3rS6UI6XRF13 yj5F3omcLSDR2Nvm9LndNUn7kfUMvgWjJfb6ImiVNmbJbZ8LjAoqpGqeKsaanP9Su63DKm17f4zo 8FzEzmk5yKlNCKzUXUFihwfic..h9UWjkeR.lDZFlNtaHvn_Ixdj.6L36eTxsZP1b6V9LxPur7pf Vmiqq3l6iSHR_Rp.dkhoRdNhLxgOw_M0Ixi_AiG3HEuqdFZVctJR1hxHrpaYoY2fs591KhoFRPhp mG1fqwcfV0mkNA11ydxQVZLOekXwu9AyxJPb4UPnMdcXxwjFUL6rwVngvwUCQZ0zL2X.8_x5GYU6 bm3sfWtUAJWQmov6vAWyI6m_MANZflP_Q1WIBl7DSpsocUwvtcSyq8utMbVDK8lxidXDSRMKjApu AYG08YFAPEK4DeIEk8dwmr36EqPsBu87AXE03.EYv9ClR21eSfYd4.UL.l7MjpCKGeB3WvfbZadx .vWJTKFo6QF1C6_YKSX7ctGuNEy0Way6wwklfcPdZeYoNvheujB.1JerpQ9PjedNl5hma03Md4Vo _nnIARTULsp.7iylhz_znj.D68OKGaSwrQQfyDUv48pWMgnWmLkt9l83cP6HT2xnQUOHPLDPHMxg rDsf_UeIcmefsImy3N0gOjveK86vd14xnKIVd0Znrn7tbEP4KNolX5evsgfmQmqJXgz49.Ynh41J Ixml52KD4ZoKonwiaYDp8YU14Gm5YGLBBQyDmTiMHMTIjTfuNDEgvbrL_WakNqOWrTziSF_t6E4O nzauTXT4FEmu_OkPLJEgUuqFG3TVfdh5iyR47Xx70gA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Tue, 26 Jun 2018 14:38:05 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp428.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4b3c61cfdadcc6f5617b6c506c7de04a; Tue, 26 Jun 2018 14:38:00 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: RPI3 swap experiments, was Re: GPT vs MBR for swap devices From: Mark Millard In-Reply-To: <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> Date: Tue, 26 Jun 2018 07:37:59 -0700 Cc: Warner Losh , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <25F1A4BA-FBFC-4C32-85DD-5F5BA71A2B1A@yahoo.com> <20180620023253.GA89924@www.zefox.net> <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> To: Jamie Landeg-Jones , bob prohaska X-Mailer: Apple Mail (2.3445.8.2) 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:38:07 -0000 On 2018-Jun-26, at 3:40 AM, Jamie Landeg-Jones = wrote: > Warner Losh wrote: >=20 >>>> _vfs_done():da0d[WRITE(offset=3D51819347968, length=3D131072)]error = =3D 5 >>>> g_vfs_done():da0d[WRITE(offset=3D51819479040, length=3D28672)]error = =3D 5 >>>> g_vfs_done():da0d[READ(offset=3D59586936832, length=3D32768)]error = =3D 5 >>>> g_vfs_done():vm_fault: pager read error, pid 823 (tcsh) >>>=20 >>=20 >> 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. >>=20 >=20 > [ ... ] >=20 >> 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... >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > (n.b. i never had swap errors, but I can't recall if i ever configured = swap on the usb > drive) The presence of the errors is a confounding variable for the other issues being looked into. It would likely be better for the effort to be split: A) Looking into the drive errors and what range of contexts get them, hoping to find something to fix the issue (such as by adding a quirk). B) Looking into the swapping and Out Of Memory process killing --but absent such errors being involved. (For now this might require a different instance of the same type of device or a different type of device.) It seems too complicated to be investigating (B) but in a context with the drive errors also involved. As I remember, Bob P. Did reproduce drive errors even without the problem drive being used for swapping. This too suggests (A) as separate activity. If only one of the 2 is targeted first, (A) may be the better one to pursue for those with reproducible examples. For those with contexts that lack the drive errors, (B) activity might show a contrasting behavior for lack of drive errors --or the behavior might be reproduced. Cross checking on if drive errors started showing up would be appropriate. An intersting question for (A) might be if some drive benchmark program(s) might reproduce the drive errors. If such was found, the context for reproduction would be far simpler than buildworld buildkernel use. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)