Hi, Santosh I think it depends on whether IRQ is enabled. It is a limitation for current L3 error logging mechanism. On Fri, Jan 14, 2011 at 3:17 PM, Santosh Shilimkar <santosh.shilimkar@xxxxxx> wrote: >> -----Original Message----- >> From: cooloney@xxxxxxxxx [mailto:cooloney@xxxxxxxxx] 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@xxxxxx> wrote: >> >> -----Original Message----- >> >> From: TAO HU [mailto:tghk48@xxxxxxxxxxxx] >> >> 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. > -- Best Regards Hu Tao -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
