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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 14, 2011 at 4:06 PM, Santosh Shilimkar
<santosh.shilimkar@xxxxxx> wrote:
>> -----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
>

Is there any testcase I can try to make sure the L3 error interrupt is working?

Thanks,
-- 
Bryan Wu <bryan.wu@xxxxxxxxxxxxx>
Kernel Developer    +86.138-1617-6545 Mobile
Ubuntu Kernel Team
Canonical Ltd.      www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux