From owner-freebsd-arm@FreeBSD.ORG Sat Sep 21 21:07:48 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 0D3D61A7 for ; Sat, 21 Sep 2013 21:07:48 +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 9D36428B8 for ; Sat, 21 Sep 2013 21:07:47 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r8LL7eDg081771; Sat, 21 Sep 2013 17:07:45 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <523E0A9C.6000505@m5p.com> Date: Sat, 21 Sep 2013 17:07:40 -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 , "freebsd-arm@freebsd.org" Subject: Re: Progress on Raspberry Pi References: <523CED09.2010509@m5p.com> <155A28EF-C877-4E21-8DAD-55B48F42A661@kientzle.com> <523DED0C.8010403@m5p.com> In-Reply-To: <523DED0C.8010403@m5p.com> Content-Type: text/plain; charset=windows-1252; 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]); Sat, 21 Sep 2013 17:07:46 -0400 (EDT) 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 21:07:48 -0000 On 09/21/13 15:01, George Mitchell wrote: > On 09/21/13 14:25, Tim Kientzle wrote: >>[...] >>> 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 It appears that "t" is the command to use here. The first one is in: http://www.m5p.com/~george/pi/trace1.txt along with kernel.tbz, which includes my /boot/kernel/kernel.symbols, /boot/kernel/kernel, and kernel/kernel.gz.tramp (don't know what that is, but my tar command picked it up). Perhaps that will help decipher the addresses in the backtrace. This one occurred while I was re-running "portmaster -BDg devel/glib20" under the script command to see why the whole "gio" include directory isn't getting installed. Using MALLOC_PRODUCTION=yes doesn't seem to have cured this problem -- George