From owner-freebsd-arm@FreeBSD.ORG Tue Nov 25 19:17:32 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE6C935B for ; Tue, 25 Nov 2014 19:17:32 +0000 (UTC) Received: from mail.FoxValley.net (mail.FoxValley.net [64.135.192.34]) by mx1.freebsd.org (Postfix) with SMTP id 89ACC9F0 for ; Tue, 25 Nov 2014 19:17:32 +0000 (UTC) Received: (qmail 6699 invoked from network) for freebsd-arm@freebsd.org; 25 Nov 2014 13:17:26 -0600 Received: from marengo.foxvalley.net (draymond@64.135.192.25) by mail.foxvalley.net with SMTP; 25 Nov 2014 13:17:26 -0600 Received: from sp5.qualcomm.com (sp5.qualcomm.com [199.106.103.55]) by webmail.FoxValley.net (Horde MIME library) with HTTP; Tue, 25 Nov 2014 13:17:26 -0600 Message-ID: <20141125131726.u0wepbqanhv0owog@webmail.FoxValley.net> Date: Tue, 25 Nov 2014 13:17:26 -0600 From: draymond@FoxValley.net To: freebsd-arm@freebsd.org Subject: re: new support for Raspberry Pi B+ MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 19:17:32 -0000 It seems that "portsnap fetch update" is a consistent way to generate =20 a panic. I have now seen panics with all four of my SD cards on two =20 different Raspberry Pis, and with three different power cables. All =20 occurred while running at low speed for SD (25MHz) on r274416. Here =20 is the latest panic: ssh output: ----------- root@raspberry-pi:~ # time portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching public key from isc.portsnap.freebsd.org... done. Fetching snapshot tag from isc.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Mon Nov 24 17:13:37 MST 2014: a9871e18baf0354c1d0795484a204847f79729af04cbfe100% of 70 MB 740 kBps 01m3= 7s Extracting snapshot... done. Verifying snapshot integrity... done. Fetching snapshot tag from isc.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Mon Nov 24 17:13:37 MST 2014 to Mon Nov 24 21:03:40 MST 2014. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 66 patches. (66/66) 100.00% done. done. Applying patches... done. Fetching 20 new ports or files... done. Removing old files and directories... console output: --------------- dev =3D mmcsd0s2a, block =3D 343613, fs =3D /root/crochet/work/_.mount.freeb= sd panic: ffs_blkfree_cg: freeing free frag KDB: enter: panic [ thread pid 8 tid 100056 ] Stopped at $d: ldrb r15, [r15, r15, r15, ror r15]! db> Ian, you mentioned that you thought this looked like a memory =20 corruption similar to the issues reported on Wandboard. I have been =20 reading those threads but I don't fully understand what is the issue. =20 Can you clarify? I also saw some discussion about some new changes =20 currently under testing and planned for release. Are these expected =20 to resolve the memory corruption? What is the root cause and is the =20 problem present in all builds or just recent builds?