From owner-freebsd-arm@freebsd.org Tue Mar 17 18:59:27 2020 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 A7EE526FCE3 for ; Tue, 17 Mar 2020 18:59:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-22.consmr.mail.ne1.yahoo.com (sonic303-22.consmr.mail.ne1.yahoo.com [66.163.188.148]) (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 48hjC21PK2z4Ssg for ; Tue, 17 Mar 2020 18:59:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: xz6ZPBMVM1mKVRqHLJJF33lYXprWRFPROTKPdHDwhf2aiHcdsXm6GvBcS.MfRM2 m7.zGBQ2m7hWbZRaG7A4GnuuobqBNc5apT6rVHPiafV7pHfKQoSi61zKzSSymx2eh.wcIZp40vZw mX9MMG3MlocJnF8GgBCqXeMFj19.7T1dsjHsFK5yO8aAKnKwyKyGR5wVliSsmuEB1ZO3Mm5j94IW Jcr3uHhcPefcRH4axXJ0H5Shy4xdDTnmTrbBHwahX7k4PqscLK4NHV0ce95GANyPe_7Z_rEe8MQq e4bQ85SXsxZx4FMMTxyXs3gHnZRVDkRbu8ZDgGoNvVJ_5ivJpQYCjOtAz5yqsq3ccLFt_WdR1lFG EQH25UXTdfq3fiGYTMFZPMfHZcaL0v.6NDm8kMd8VfhuD8UYvwTA7qC4YcFySBT2nqR.Ti5ETAK2 rTP1xVPWlUk6XKeLFFvhzs6cEsc7Z4C5p9Q73MGN7n3eoMAoZeROwixNByeMqVcJ9oHfsrOkqvJn iNsM16dUV5BEDzTGTDR08Xha_IM24a.mDoI1qwSZxk8OMSrGUPZFoI3Sv5TdnqNTBDPKjxw5LqyX vGoGfb64P1L__T54Od9Lsa.YJ9FS0EXW.WAIfytWfvRfNO4_iPnOUqvLDcyrFWM9Pu2bT86knQDN eas7LwspC.AodwbEeb8BeNT8.WOpTfFvNbwqHx_9UL.hvuhjkGb25fDbNV9AAHUVjZIWF6j1gGEC Rag3Ys8oqUZVJdZjH9lHGlI9gBywZM2mmy12sDc.v4f4MV78EsEuKPjiIzbl04aSo7gnF0ma99Lw Cf1XJpHT2w3M24BDWFptg2CUz3JAtMpLxDdfb8az4.0itA6_qIlMbEYVyAKj3JXBmxqBxJS5eSxl LgyMzSZOORki_soS2MkvfiekcCPInx4GhDUrS_RIKxJU3_DTs34HTvKQKWLxNa.4OdkehFZRLcTT b2V_BSU7KtoEapbDh2G2qthrQ6F50S.k_SS8MwrexRyxTfbnVymbb5OHWZHyKyWlHMb9vI2rZHIK 4MGLxhT0PKccFtywYueaPIrdzCC5DJjC4IrA3obwjE1Mzuo6WhayV_sQMgJu9xyznVU76QU1EZjw 9QOhHk9WxWWzAoJjjRNvxhB_GTHovqEDXN34S53lyjW6G_Lx8sWZiWk673Z0wiCMqqJdy3gEy27v bXJ4dednpvKJ19uU184ePBTwkO_8kvX5wF7SpzGXXstsOpnfL7JL43ofhivNsDmkQQcHxH7Tq_Tx qS6GCV5Yj3.lOpY7QCGIZ0jet7r4eFApimjPMhy1SsSYhruGH3jZQ_lENUc_MmgGr51PTkcP5jP8 j6XP9DfO7XIVVl.4Dj8pF5S_vtzexht3CCjdTIZWnt6U7eRqFaHNXgO58eICnWVD1Iupi4YjLcjn iJz0IXS6i_w-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ne1.yahoo.com with HTTP; Tue, 17 Mar 2020 18:59:24 +0000 Received: by smtp432.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID df04ead83b850a4ebb123f4d6783c163; Tue, 17 Mar 2020 18:59:18 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Subject: Re: Pine64+2GB status? Is anyone else having the following sort of panic problem? Date: Tue, 17 Mar 2020 11:59:17 -0700 References: <521CDF7F-8F5F-4E92-8BFE-3E39E1A00586@yahoo.com> To: freebsd-arm In-Reply-To: <521CDF7F-8F5F-4E92-8BFE-3E39E1A00586@yahoo.com> Message-Id: <3B9DF93B-6E7E-49B2-B253-DE268317323E@yahoo.com> X-Mailer: Apple Mail (2.3608.60.0.2.5) X-Rspamd-Queue-Id: 48hjC21PK2z4Ssg X-Spamd-Bar: ++ X-Spamd-Result: default: False [2.48 / 15.00]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:36646, ipnet:66.163.184.0/21, country:US]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (2.52), ipnet: 66.163.184.0/21(1.18), asn: 36646(0.94), country: US(-0.05)]; NEURAL_SPAM_MEDIUM(0.99)[0.988,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE_FREEMAIL(0.00)[]; NEURAL_SPAM_LONG(0.99)[0.991,0]; RCVD_IN_DNSWL_NONE(0.00)[148.188.163.66.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_POSSIBLE(0.00)[148.188.163.66.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2] 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, 17 Mar 2020 18:59:27 -0000 On 2020-Mar-15, at 00:49, Mark Millard wrote: > In recent times I've had access to the Pine64+ 2GB again > and when lots of data is being copied to the mmcsd0 > UFS partition (various new and old mmcsd media examples) > I eventually get the following sort of failure: > > aw_mmc0: controller timeout > mmcsd0: Error indicated: 1 Timeout > panic: vm_fault_lookup: fault on nofault entry, addr: 0xffff00004ee1c000 > cpuid = 1 > time = 1584255814 > KDB: stack backtrace: > db_trace_self() at db_trace_self_wrapper+0x28 > pc = 0xffff00000082617c lr = 0xffff00000010aec0 > sp = 0xffff0000402ece30 fp = 0xffff0000402ed040 > > db_trace_self_wrapper() at vpanic+0x194 > pc = 0xffff00000010aec0 lr = 0xffff00000046e120 > sp = 0xffff0000402ed050 fp = 0xffff0000402ed0f0 > > vpanic() at panic+0x44 > pc = 0xffff00000046e120 lr = 0xffff00000046df88 > sp = 0xffff0000402ed100 fp = 0xffff0000402ed180 > > panic() at vm_fault+0x1ff4 > pc = 0xffff00000046df88 lr = 0xffff0000007b4d1c > sp = 0xffff0000402ed190 fp = 0xffff0000402ed2c0 > > vm_fault() at vm_fault_trap+0x64 > pc = 0xffff0000007b4d1c lr = 0xffff0000007b2c14 > sp = 0xffff0000402ed2d0 fp = 0xffff0000402ed310 > > vm_fault_trap() at data_abort+0x108 > pc = 0xffff0000007b2c14 lr = 0xffff000000844dec > sp = 0xffff0000402ed320 fp = 0xffff0000402ed3d0 > > data_abort() at do_el1h_sync+0x144 > pc = 0xffff000000844dec lr = 0xffff000000843e38 > sp = 0xffff0000402ed3e0 fp = 0xffff0000402ed410 > > do_el1h_sync() at handle_el1h_sync+0x78 > pc = 0xffff000000843e38 lr = 0xffff000000828878 > sp = 0xffff0000402ed420 fp = 0xffff0000402ed530 > > handle_el1h_sync() at bounce_bus_dmamap_sync+0x210 > pc = 0xffff000000828878 lr = 0xffff0000008246a0 > sp = 0xffff0000402ed540 fp = 0xffff0000402ed620 > > bounce_bus_dmamap_sync() at aw_mmc_request+0x3d0 > pc = 0xffff0000008246a0 lr = 0xffff0000007f1188 > sp = 0xffff0000402ed630 fp = 0xffff0000402ed670 > > aw_mmc_request() at mmc_wait_for_request+0x12c > pc = 0xffff0000007f1188 lr = 0xffff0000001f2b80 > sp = 0xffff0000402ed680 fp = 0xffff0000402ed6d0 > > mmc_wait_for_request() at mmcsd_rw+0x198 > pc = 0xffff0000001f2b80 lr = 0xffff0000001fc010 > sp = 0xffff0000402ed6e0 fp = 0xffff0000402ed810 > > mmcsd_rw() at mmcsd_task+0x2b0 > pc = 0xffff0000001fc010 lr = 0xffff0000001fabe8 > sp = 0xffff0000402ed820 fp = 0xffff0000402ed940 > > mmcsd_task() at fork_exit+0x90 > pc = 0xffff0000001fabe8 lr = 0xffff00000041fd78 > sp = 0xffff0000402ed950 fp = 0xffff0000402ed980 > > fork_exit() at fork_trampoline+0x10 > pc = 0xffff00000041fd78 lr = 0xffff000000843b6c > sp = 0xffff0000402ed990 fp = 0x0000000000000000 > > KDB: enter: panic > [ thread pid 20 tid 100078 ] > Stopped at arm64_dcache_wb_range+0x18: undefined d50b7a20 > > I've never had this happen quickly or for a small amount > of data. > > The same operations done with the same examples of media > work fine in the Rock64 (same buildworld and buildkernel > results installed, booted, and operating for both boards). > > Both boards have fans and heatsinks and such. > > The specific example is from head -r358510 but I've seen > it on -r358132 as well. (I'd not used the Pine64+2GB in > a long time prior to that so I've no useful clue when > this started.) > > Is anyone else seeing such oddities? Leaving the Pine64+2GB powered on and booted but idle (but for default background processing that happens) still can get such crashes. The example below is from head -r358966 . Sometimes there is more than one timeout notice first . . . aw_mmc0: controller timeout mmcsd0: Error indicated: 1 Timeout aw_mmc0: controller timeout mmcsd0: Error indicated: 1 Timeout aw_mmc0: controller timeout mmcsd0: Error indicated: 1 Timeout panic: vm_fault_lookup: fault on nofault entry, addr: 0xffff00004eacc000 cpuid = 2 time = 1584440665 KDB: stack backtrace: . . . (I'll not repeat the backtrace) . . . === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)