RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort

[Santosh Shilimkar <santosh.shilimkar@ti.com>]

> -----Original Message-----
> From: cooloney@gmail.com [mailto:cooloney@gmail.com] On Behalf Of
> Bryan Wu
> Sent: Friday, January 14, 2011 11:24 PM
> To: Santosh Shilimkar
> Cc: TAO HU; TAO HU; linux-omap
> Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
>
> On Fri, Jan 14, 2011 at 4:06 PM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
> >> -----Original Message-----
> >> From: TAO HU [mailto:tghk48@motorola.com]
> >> Sent: Friday, January 14, 2011 1:29 PM
> >> To: Santosh Shilimkar
> >> Cc: Bryan Wu; TAO HU; linux-omap
> >> Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external
> abort
> >>
> >> Hi, Santosh
> >>
> >> I think it depends on whether IRQ is enabled.
> >> It is a limitation for current L3 error logging mechanism.
> >>
> > L3 IRQ is always enabled except low power states. I guess
> > we patched this part as well so that error is not lost and
> > its logged.
> >
> > It's not a limitation L3 interrupt but behavior of CPU.
> > Because scenario's where the I bit is cleared at CPU level
> > (Interrupt disable), it's immune to interrupts.
> >
> > Note the interrupt is not lost but just got delayed a bit
> >
>
> Is there any testcase I can try to make sure the L3 error interrupt
> is working?
>
I guess with simple readmem to some non-initalised modules should
trigger the error. Just read the change log of the patch. I guess
there are couple of examples