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 12:47:10 +0530 [thread overview]
Message-ID: <c77cce3143f47a793057b2a9a90a277b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimA3Ypk6HH=Gn+wU-1-_mqF184tx-uvAtJ4Pac5@mail.gmail.com>
> -----Original Message-----
> From: cooloney@gmail.com [mailto:cooloney@gmail.com] On Behalf Of
> Bryan Wu
> Sent: Friday, January 14, 2011 3:08 AM
> To: Santosh Shilimkar
> Cc: TAO HU; TAO HU; linux-omap
> Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external abort
>
> On Wed, Nov 24, 2010 at 2:23 PM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
> >> -----Original Message-----
> >> From: TAO HU [mailto:tghk48@motorola.com]
> >> Sent: Wednesday, November 24, 2010 11:40 AM
> >> To: Santosh Shilimkar
> >> Cc: TAO HU; Bryan Wu; linux-omap
> >> Subject: Re: OMAP4 ES2.0 Unhandled fault: imprecise external
> abort
> >>
> >> Hi, Santosh
> >>
> >> Could you point out the specific kernel option for "L3 error
> debugging"?
> >>
> > System Type --->
> > [*] Enable L3 error logging
> >
>
> I've enabled that for my Panda kernel. How to get the error log? I
> still got the same "Unhandled fault: imprecise external abort"
> message. Maybe L3 does not have any error at all.
>
Strange. It should have triggered an L3 eror interrupt.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-14 7:17 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 [this message]
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
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=c77cce3143f47a793057b2a9a90a277b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox