From owner-freebsd-arm@FreeBSD.ORG Sat Sep 21 01:22:01 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 06AEE9D for ; Sat, 21 Sep 2013 01:22:01 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C0DCF2E41 for ; Sat, 21 Sep 2013 01:22:00 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r8L1LsId072900; Fri, 20 Sep 2013 21:21:59 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <523CF4B2.6030409@m5p.com> Date: Fri, 20 Sep 2013 21:21:54 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130716 Thunderbird/17.0.7 MIME-Version: 1.0 To: Luiz Otavio O Souza Subject: Re: Progress on Raspberry Pi References: <523CED09.2010509@m5p.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Fri, 20 Sep 2013 21:21:59 -0400 (EDT) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Sep 2013 01:22:01 -0000 On 09/20/13 21:16, Luiz Otavio O Souza wrote: > On 20 September 2013 21:49, George Mitchell > wrote: > > My AdaFruit serial cable arrived, so now I can gather useful information > when my RPi crashes (which is still happening fairly often as I try to > build print/cups, having started five days ago and still not having > gotten through ghostscript). > > I built my image with crochet on an amd64 running r255361, and the image > itself is based on that version. (However, in sys/arm/arm I updated > pmap-v6.c to 255612 and stdatomic.c to 255613. I see they have been > updated again within the last day; perhaps I should try again.) > > /etc/src.conf: > MALLOC_PRODUCTION=yes > > > MALLOC_PRODUCTION=yes is just a workaround for the RPi problem, in a > ideal world (where everything works) we wouldn't need to set it. > > > /etc/make.conf: > WITH_PKGNG=yes > MALLOC_PRODUCTION=yes > # added by use.perl 2013-08-20 10:11:49 > PERL_VERSION=5.14.4 > > I commented out the five syscons-related lines in sys/arm/conf/RPI-B so > I could use the serial port. My SDHC card is apparently on the hairy > edge of working, so I definitely needed /boot/loader.conf to contain: > hw.bcm2835.sdhci.hs=0. Before I added that, I ended up with the dreaded > error 19 and a manual mountroot prompt, at which point mountroot would > accept a character from the serial input about 1/4 of the time. Other > serial input works without a problem. > > > Can you check if the patch on arm/179688 > (http://www.freebsd.org/cgi/query-pr.cgi?pr=arm/179688) fix the > mountroot input problem for you ? I'll try that. > > > Before I remembered to comment out the /dev/ttyvN lines in /etc/tty, I > naturally saw getty errors on the nonexistent devices, but I would also > randomly get an "Interrupted system call" on /dev/ttyu0, followed by a > long pause, followed (finally) by a login prompt. After I commented out > the ttyvN lines, the "Interrupted system call" error on /dev/ttyu0 went > away. > > > This is added by crochet, isn't ? (boards/RaspberryPi/overlay/etc/ttys) > > > Questions: > > 1. Do we have any sort of a memory test for the RPi? It seems unlikely > that I have a hardware problem, but I would like to rule it out. > > > 2. Now that I can do something when I get the prefetch abort or panic, > what should I do at the "db>" prompt to help debug it? It's happening > about five or six times a day. > > > We have a known bug that triggers under heavy load (during builds): > http://www.freebsd.org/cgi/query-pr.cgi?pr=arm/182060 > > We need to check (now that gcc builds should be working again for arm) > if there is any difference between the builds with clang and gcc, oabi > and eabi. > > Thanks, > Luiz Back in January, gcc worked fine. More recently, not so fine, and I finally gave up and plunged into the clang/EABI world. It mostly works aside from my crashes. -- George