Re: earmhf issues on Beaglebone Black

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Jul 15, 2014 at 02:43:45PM -0700, Matt Thomas wrote:
> 
> On Jul 15, 2014, at 12:43 PM, Manuel Bouyer 
> <bouyer%antioche.eu.org@localhost> wrote:
> 
> > OK. I though it could maybe come from the ethernet driver,
> > but it looks like the "data abort" messages points more to a MMU issue ...
> 
> Could also be an alignment issue.
> 
> # sysctl -w machdep.printfataltraps=1
> 
> will turn dumping of the trap (exception frame) for fatal errors.

I have the problem too; here's what I got:
data_abort_handler: data_aborts fsr=0x186e far=0x7fffb890
23012.1(sh): trap: signo=10 code=2 addr=0x7fffb890 trap=0x186e
r0=40202ce8 r1=00000000 r2=00001544 r3=401ffcbc
r4=00000000 r5=00000000 r6=00000000 r7=403644f4
r8=40322400 r9=ffffffff rA=00032f00 rB=7fffb8b4
ip=7fffb8a0 sp=7fffb8a0 lr=40175ea4 pc=400d2150 spsr=60000010

Note that not all data_abort_handler printfs cause a verbose output.
Here's a complete console log since I set printfataltraps to 1:
login: data_abort_handler: data_aborts fsr=0x83e far=0x40042000
data_abort_handler: data_aborts fsr=0x186e far=0x7fffb890
23012.1(sh): trap: signo=10 code=2 addr=0x7fffb890 trap=0x186e
r0=40202ce8 r1=00000000 r2=00001544 r3=401ffcbc
r4=00000000 r5=00000000 r6=00000000 r7=403644f4
r8=40322400 r9=ffffffff rA=00032f00 rB=7fffb8b4
ip=7fffb8a0 sp=7fffb8a0 lr=40175ea4 pc=400d2150 spsr=60000010
data_abort_handler: data_aborts fsr=0x186e far=0x7fffc160

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--