From owner-freebsd-arm@FreeBSD.ORG Sat Oct 12 01:14:17 2013 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DF5EBE01; Sat, 12 Oct 2013 01:14:17 +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 78EF12F68; Sat, 12 Oct 2013 01:14:17 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r9C1E6SF008810; Fri, 11 Oct 2013 21:14:15 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <5258A25E.1090903@m5p.com> Date: Fri, 11 Oct 2013 21:14:06 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Raspberry Pi prefetch aborts References: <5254AC6C.9070400@m5p.com> <1381518610.1130.155.camel@revolution.hippie.lan> In-Reply-To: <1381518610.1130.155.camel@revolution.hippie.lan> 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, 11 Oct 2013 21:14:15 -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, 12 Oct 2013 01:14:17 -0000 On 10/11/13 15:10, Ian Lepore wrote: > On Tue, 2013-10-08 at 21:07 -0400, George Mitchell wrote: >> Am I the only one seeing these? >> >>[...] > Are you the only one seeing these? Yes, or no, or maybe. [...] > > In the future, no need to post a whole backtrace, because it's always > the same. (Well, if you ever saw one where the exception_exit frame > didn't backlink to spinlock_exit, that would be interesting.) The crash > info that is most useful for this problem is this register dump block: > > Fatal kernel mode prefetch abort at 0x4278f502 >> trapframe: 0xdd2eafa0, spsr=200000f3 >> r0 =00000001, r1 =00000001, r2 =00000001, r3 =c058dbd0 >> r4 =c2400000, r5 =00000004, r6 =c05826a0, r7 =c2400308 >> r8 =c058d8c8, r9 =c25fd300, r10=c29aa9e4, r11=0004240c >> r12=00000000, ssp=dd2eaff0, slr=c046079c, pc =4278f502 >> >> [ thread pid 27951 tid 100090 ] >> Stopped at 0x4278f502: address 0x4278f502 is invalid > > Also, next time it happens it might be good to see the output of these > commands: > show all procs > show proc PID > show thread TID > > where PID and TID are the pid and tid numbers from the end of the > register dump block. > > -- Ian > Ian, thanks for your efforts, and I wish you good luck! I'll definitely try these commands the next time it happens (though it might not be for another couple of weekends). -- George