From owner-freebsd-arm@FreeBSD.ORG Sat Sep 21 19:01:39 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 CD4A2E6E for ; Sat, 21 Sep 2013 19:01:39 +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 941972361 for ; Sat, 21 Sep 2013 19:01:39 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r8LJ1WjO080888; Sat, 21 Sep 2013 15:01:37 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <523DED0C.8010403@m5p.com> Date: Sat, 21 Sep 2013 15:01:32 -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: Tim Kientzle Subject: Re: Progress on Raspberry Pi References: <523CED09.2010509@m5p.com> <155A28EF-C877-4E21-8DAD-55B48F42A661@kientzle.com> In-Reply-To: <155A28EF-C877-4E21-8DAD-55B48F42A661@kientzle.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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]); Sat, 21 Sep 2013 15:01:38 -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 19:01:40 -0000 On 09/21/13 14:25, Tim Kientzle wrote: > > On Sep 20, 2013, at 5:49 PM, George Mitchell wrote: > >> My AdaFruit serial cable arrived, so now I can gather useful information >> when my RPi crashes… > > Excellent! > >> 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 >> >> /etc/make.conf: >> WITH_PKGNG=yes >> MALLOC_PRODUCTION=yes >> # added by use.perl 2013-08-20 10:11:49 >> PERL_VERSION=5.14.4 > > By default, Crochet ignores the host /etc/src.conf > and /etc/make.conf on the assumption that what > is right for the host system is not necessarily correct > for the target system. > > If you specifically want to use them, you can add > > SRCCONF=/etc/src.conf > __MAKE_CONF=/etc/make.conf > > to your configuration file. Of course, you can also put > src.conf and make.conf files elsewhere for Crochet to use. Thanks! I put that in my crochet config file just a couple of weeks ago when you first mentioned it. > >> 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. > > Keyboard input to mount root seems to > be broken on a lot of FreeBSD systems. > >> Before I remembered to comment out the /dev/ttyvN lines in /etc/tty,… > > Should Crochet's RaspberryPi configuration disable those? Not sure. Before I got the serial cable hooked up, it was nice to be able to use the USB keyboard to log into the system. > >> 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. > > Type "bt" to get a backtrace. That's the single most informative > thing. Note: The first few stack frames displayed are from inside > the debugger itself and aren't particularly interesting. The important > frames are a little later where we see *why* we ended up in the > debugger. > > Tim > Okay, will do. I'll try to collect a few and maybe post them in the few days. Any predictions of what will happen if I try to compile and install x11/xorg on the RPi? -- George