Date: Fri, 11 Oct 2013 21:14:06 -0400 From: George Mitchell <george+freebsd@m5p.com> To: Ian Lepore <ian@FreeBSD.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@FreeBSD.org> Subject: Re: Raspberry Pi prefetch aborts Message-ID: <5258A25E.1090903@m5p.com> In-Reply-To: <1381518610.1130.155.camel@revolution.hippie.lan> References: <5254AC6C.9070400@m5p.com> <1381518610.1130.155.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5258A25E.1090903>