[PATCH] ARM: keystone: add a work around to handle asynchronous external abort
l.stach at pengutronix.de
Tue Aug 18 01:28:20 PDT 2015
Am Dienstag, den 18.08.2015, 09:13 +0100 schrieb Russell King - ARM
> On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilimkar at oracle.com 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.
At least one of the Marvell platforms has the same issue with the
bootloader (I think it is some downstream U-Boot) leaving an imprecise
abort hanging around as a nice present for Linux to crash on.
If it turns out to be the same issue the only kernel level workaround
would be to ignore exactly 1 abort after bootup.
Then we still need a solution for the platform and the PCIe driver abort
handler both hooking into the same abort vector, which won't work
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
More information about the linux-arm-kernel