On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilim...@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. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
