Re: earmhf issues on Beaglebone Black

[Matt Thomas <matt%3am-software.com@localhost>]

On Jul 22, 2014, at 3:05 PM, Manuel Bouyer <bouyer%antioche.eu.org@localhost> 
wrote:

> On Tue, Jul 22, 2014 at 02:58:39PM -0700, Matt Thomas wrote:
>> 
>> On Jul 22, 2014, at 2:45 PM, Manuel Bouyer 
>> <bouyer%antioche.eu.org@localhost> wrote:
>> 
>>> AFAIK uvm_fault() is not called.
>>> we enter data_abort_handler() with (fsr & FAULT_TYPE_MASK) == 0xe.
>>> At line 278, data_aborts[fsr & FAULT_TYPE_MASK].func is not NULL
>>> (it's dab_buserr() ) so we call it and goto to either do_trapsignal or out.
>>> 
>>> I just checked, both freebsd and linuxn handle fsr & FAULT_TYPE_MASK) == 0xe
>>> as we do, I didn't see anything special.
>> 
>> I don't understand why the fault type is 0xe.  it should be 0x5.
>> 
>> can you print armreg_ttbr_read() and pm->pm_l1 as well?
> 
> Sure, here it is:
> data_abort_handler: data_aborts fsr=0x80e far=0x20000
> dab_buserr far 0x20000 -> NULL pm->pm_l1[far >> L1_S_SHIFT] = 0x0
> pm->pm_l1 0x9f036000 armreg_ttbr_read() 0x9f03601b

What happens if you change the [14] entry to NULL?