On Tue, 18 Aug 2015 09:13:34 +0100Yes, in normal world (Non secure supervisor)
Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> wrote:
On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilimkar@xxxxxxxxxx wrote:
From the logs this seems to be mostly clock related issue for some
peripheral. If the bootloader clock enable all hack still exists,
may be you can try that out.
Another way to debug this is to start disabling peripheral drivers
from the kernel 1 by 1 and see if the issue goes away.
Highly unlikely to make any difference. As the failure happens soo early
with the patch applied, the kernel hasn't had much of a chance to touch
the hardware - about the only things are the decompressor and the kernel
touching the early console. As they seem to be working, it suggests
that's not the cause.
It seems to be pointing towards something in the boot loader...
Normally, uboot will hook itself into the vectors to report errors, but
I wonder whether uboot enables asynchronous aborts while it's running.
Don't forget to make sure that the aborts are disabled again prior to
calling the kernel.
Another possible cause: trustzone software.
we root caused such kind of asynchronous external abort on Marvell Berlin SoCs
to a trustzone bug. I'm not sure whether keystone linux is running at normal
world or not.