Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752765AbbHRMGX (ORCPT ); Tue, 18 Aug 2015 08:06:23 -0400 Received: from mail-pa0-f47.google.com ([209.85.220.47]:35760 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751295AbbHRMGW (ORCPT ); Tue, 18 Aug 2015 08:06:22 -0400 Date: Tue, 18 Aug 2015 17:36:18 +0530 From: Afzal Mohammed To: Lucas Stach Cc: Russell King - ARM Linux , "santosh.shilimkar@oracle.com" , Murali Karicheri , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, ssantosh@kernel.org Subject: Re: [PATCH] ARM: keystone: add a work around to handle asynchronous external abort Message-ID: <20150818120618.GA4294@afzalpc> 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> <1439886500.31432.4.camel@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1439886500.31432.4.camel@pengutronix.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1220 Lines: 31 Hi Murali, On Tue, Aug 18, 2015 at 10:28:20AM +0200, Lucas Stach wrote: > Am Dienstag, den 18.08.2015, 09:13 +0100 schrieb Russell King - ARM > Linux: > > 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 you have a JTAG, maybe you can manually set CPSR.A bit (equivalent of Lucas's patch) at bootloader/kernel entry and conclude who is the culprit or maybe even localize it better. This method did help in rootcausing issue in one of the SoC that showed the same behaviour. Regards Afzal -- 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/