From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: TAO HU <tghk48@motorola.com>, TAO HU <taohu@motorola.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: RE: OMAP4 ES2.0 Unhandled fault: imprecise external abort
Date: Fri, 14 Jan 2011 23:31:34 +0530 [thread overview]
Message-ID: <b5cc87170d3e76e0cf62b3dfda70ffc2@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinwK9GtVUiUFeE=75cjyOLb5dzVhdGQHzPKCzQw@mail.gmail.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
prev parent reply other threads:[~2011-01-14 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 3:11 OMAP4 ES2.0 Unhandled fault: imprecise external abort TAO HU
2010-11-24 4:21 ` Bryan Wu
2010-11-24 4:34 ` TAO HU
2010-11-24 4:44 ` Bryan Wu
2010-11-24 5:40 ` Santosh Shilimkar
2010-11-24 6:09 ` TAO HU
2010-11-24 6:23 ` Santosh Shilimkar
2011-01-13 21:38 ` Bryan Wu
2011-01-14 7:17 ` Santosh Shilimkar
2011-01-14 7:58 ` TAO HU
2011-01-14 8:06 ` Santosh Shilimkar
2011-01-14 17:54 ` Bryan Wu
2011-01-14 18:01 ` Santosh Shilimkar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5cc87170d3e76e0cf62b3dfda70ffc2@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=bryan.wu@canonical.com \
--cc=linux-omap@vger.kernel.org \
--cc=taohu@motorola.com \
--cc=tghk48@motorola.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.