Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753259AbbHROuI (ORCPT ); Tue, 18 Aug 2015 10:50:08 -0400 Received: from devils.ext.ti.com ([198.47.26.153]:41271 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751755AbbHROuG (ORCPT ); Tue, 18 Aug 2015 10:50:06 -0400 Message-ID: <55D345FF.3010707@ti.com> Date: Tue, 18 Aug 2015 10:49:35 -0400 From: Murali Karicheri Organization: Texas Instruments User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Jisheng Zhang , Russell King - ARM Linux CC: "santosh.shilimkar@oracle.com" , , , Subject: Re: [PATCH] ARM: keystone: add a work around to handle asynchronous external abort References: <1439320409-20084-1-git-send-email-m-karicheri2@ti.com> <55CDF579.4050408@ti.com> <20150814140934.GX7557@n2100.arm.linux.org.uk> <55CE05EC.4040909@oracle.com> <55CE633C.10402@ti.com> <20150814215617.GA7557@n2100.arm.linux.org.uk> <55D25C64.3090107@ti.com> <55D2A1DD.9000007@oracle.com> <20150818081334.GK7557@n2100.arm.linux.org.uk> <20150818162858.42035da0@xhacker> In-Reply-To: <20150818162858.42035da0@xhacker> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1746 Lines: 43 On 08/18/2015 04:28 AM, Jisheng Zhang wrote: > On Tue, 18 Aug 2015 09:13:34 +0100 > Russell King - ARM Linux wrote: > >> On Mon, Aug 17, 2015 at 08:09:17PM -0700, santosh.shilimkar@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. >> > > 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. Yes, in normal world (Non secure supervisor) > -- Murali Karicheri Linux Kernel, Keystone -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/