> -----Original Message----- > From: TAO HU [mailto:tghk48@xxxxxxxxxxxx] > 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 -- 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
